go-gitea/gitea

Better CI Integration

MorphBonehunter opened this issue · 13 comments

MorphBonehunter commented

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:

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

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.

BlackVoid commented

Duplicate of #357?

lunny commented

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

BlackVoid commented

Fair enough

tboerger commented

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

MorphBonehunter commented

Couldn't find something similar in the open issues.

bkcsoft commented

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

  • 👍3
strk commented

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 ?

lafriks commented

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

iddm commented

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.


  • 👍50
vijfhoek commented

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:

image

  • 👍2
  • ❤️3
stale commented

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.

NotAFile commented

this issue is still relevant

  • 👍21