CI status with hook

[hickscorp]

This feature request might not be one of the most easy, and is related to #5

The idea would be for Gogs to expose a simple API for continuous integration / deliveries system to be able to report back about specific commits / PR quality.

An example of how you set up Github to talk with Travis is explained here: http://stackoverflow.com/questions/19810386/showing-travis-build-status-in-github-repo

Basically, i have right now Gogs talk with my CI server in one way, to trigger builds within the CI system. What i would like to do is being able to configure the other way-communication, to allow Gogs to have visibility wether a specific commit / PR passes or fails the tests.

The exposed API should be template-based, or simple enough to be hook-able to any other web-hook based system, this way anyone could configure gogs with his favorite CI / CD system.

Tell me if i'm clear enough, i don't have the exact word for this process.

[hickscorp]

@unknwon If you need more informations about this feature, i can provide you with good pointers. I have created a test project on my personnal server with a pull request. The pull request triggered a strider build, which in turn used the github-status plugin to send the result back to github.

• You can see the Github result here: https://github.com/hickscorp/test/pull/5
• The CI server build for this PR was here: https://ci.pierreqr.fr/hickscorp/test/job/54a4522e4a46b7cb1f2b8ccf

Hope this will help if you're not familiar with the idea.

[kageurufu]

👍 for this

[bhchew]

+1 Also just to clarify, will the hook be triggered during a PR submit or during accepting a PR (merge)?

[cusspvz]

+1

[ekozan]

+1

[scruplelesswizard]

Has anyone started doing any work on this or is it still available?

[unknwon]

@thecanadianbaker I don't think anyone one is working on it, but it is also not a easy thing to implemented (involves design concepts of Gogs, and such.).

[scruplelesswizard]

I agree that the proposed is not easily implemented, but I think we might
be looking at it the wrong way. I think that a much simpler implementation
would be to leave the responsibility of recording and storing the
information regarding builds with the build engine, and instead have Gog's
request that information using a standard internal interface at the time of
display. That means that we can implement a common interface within Gogs to
make the build status request using some standardized parameters, but it is
up to the implementing package to manage the interaction with the build
server.

Is this feasible and does it sound appropriate?
On Mon, Feb 29, 2016 at 6:19 AM 无闻 notifications@github.com wrote:

@thecanadianbaker https://github.com/thecanadianbaker I don't think
anyone one is working on it, but it is also not a easy thing to implemented.

—
Reply to this email directly or view it on GitHub
#813 (comment).

[unknwon]

@thecanadianbaker This feature should be a part of the entire new system like GitHub's pull request merge checks.

Just the hook is easy, but that's not very extendable.

[naggie]

Very glad to see this has been added to a milestone. Great, thanks!

[migibert]

+1

[renewsorensen]

+1

[farooq-khan-nxt]

+1
Something like when you raise a Pull request CircleCI automatically builds and lets us know if pull request will pass build or fail.
And after the Pull Requests is merged again builds

[hz]

+n, n > 好多好多。 gogs后面的团队好给力。

[neithere]

I don't see how Gogs could have any practical value without this feature.

[strk]

How github implements this: https://developer.github.com/v3/repos/statuses/

[tboerger]

IMHO this feature can be integrated quite easy if you do it like github

[cblomart]

Would realy love to see this type of integration!
This allows a more automated control of what enters a repo. (coding style / tests / build). All automaticaly reported :)
👍

[kmadel]

Is anyone working on this one yet?

[strk]

On September 2, 2016 5:46:06 PM CEST, Kurt Madel notifications@github.com wrote:

Is anyone working on this one yet?

Not me. Planning to start?
--strk;

Sent from hand-held device, sorry for brevity

[unknwon]

Merge this thread to #4631.