Gitea: Better CI Integration

Created on 21 Feb 2017 · 13Comments · Source: go-gitea/gitea

Description

I'm using drone as CI System at the moment (test run) and actually i can not see if an repository has CI enabled (besides i look into the repo settings webhooks) or the build status.
Only posibility is to include the drone repo badget into the readme.md.

So it would be nice if the build status could be implemented into:

[x] the pull request like github does (it also works for drone, you use it :smile: ) #2519 #3588 #7481
[x] the commit history like Gitlab (Example)
[x] in the Main Repo Page as state of the last build (also like gitlab "passed" badget)
[x] in the commit itself if you show them in gitea

kinfeature revieweconfirmed

Source

MorphBonehunter

👍39

Most helpful comment

I'd also love the status being shown right on the pull request's page as in github. Also, it would be nice to prevent merging of commits if the CI have not build it successfully yet.

vityafx on 23 Feb 2018

👍50

All 13 comments

BTW, i'm not sure if this require also work on the drone project, but maybe if there is an plan how this could be implemented and the requirements are know, i could also open an request on the drone issue tracker.

MorphBonehunter on 21 Feb 2017

Duplicate of #357?

BlackVoid on 21 Feb 2017

It's not the same thing. One is for API, one is on the UI before the commit.

lunny on 21 Feb 2017

Fair enough

BlackVoid on 21 Feb 2017

I'm sure we already got an issue for that.

tboerger on 21 Feb 2017

Couldn't find something similar in the open issues.

MorphBonehunter on 21 Feb 2017

All of those needs #357 though, this is an extension on that 🙂

bkcsoft on 22 Feb 2017

👍3

Status API (#357) is reported as being merged by now, so what are we missing to show status in UI ?
And to have Drone update statuses ?

strk on 7 Jan 2018

@strk drone does already update status. What we miss is #2519

lafriks on 7 Jan 2018

I'd also love the status being shown right on the pull request's page as in github. Also, it would be nice to prevent merging of commits if the CI have not build it successfully yet.

vityafx on 23 Feb 2018

👍50

For what it's worth, I made a userscript to bridge the gap until #2519 is merged. It currently only shows a status on the PR page itself, but it'll do:

sijmn on 4 Jan 2019

❤3 👍2

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.