ci.jenkins.io - maintainers can now re-run build via checks

[Tim Jacomb]

Hi all

Just an update to let you know that you can now re-run failed builds via GitHub checks on ci.jenkins.io.

(Only maintainers, i.e. write access can do this, authors need to push a code change or close / reopen)

This is made possible with the GitHub checks plugin, by Kezhi as part of GSoC.

See Kezhi's blog post for more details: https://www.jenkins.io/blog/2020/08/31/github-checks-api-plugin-coding-phase-3/ 

Thanks

Tim

[Arnaud Héritier]

Awesome 🙌

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicXBAQKwaZJSMwkhAdhi_XeBfH%2BkwwsvkHWaYc2_OzvVQ%40mail.gmail.com.

--

Arnaud Héritier

Twitter/Skype : aheritier

[globero]

Great! Thank you.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_32-XbVtwrnEEdMZ%2B6eEd4ju14dUueMUk5nOjUc6DLJw%40mail.gmail.com.

[Manuel Ramón León Jiménez]

Great, thank you for the heads up.

On Tue, Sep 8, 2020 at 9:55 AM Arnaud Héritier <aher...@gmail.com> wrote:

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_32-XbVtwrnEEdMZ%2B6eEd4ju14dUueMUk5nOjUc6DLJw%40mail.gmail.com.

[Jesse Glick]

On Tue, Sep 8, 2020 at 3:53 AM Tim Jacomb <timja...@gmail.com> wrote:
> Just an update to let you know that you can now re-run failed builds via GitHub checks on ci.jenkins.io.

Does not seem to work. The message

> You have successfully requested Jenkins be rerun.

appears, but no new build starts. I have heard reports from others
trying it that it does not work for them either.

[Tim Jacomb]

I think that sometimes it resolves the wrong commit and triggers the master build, I believe Kezhi posted on the GitHub forums to ask about the expected payload here, can’t find the link atm now 

--

You received this message because you are subscribed to the Google Groups "Jenkins Infrastructure" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-infr...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/CANfRfr0bR%3DA-GRmRf3a1-ZLgbhdL4Y3rXcQFRMxki%2Bo2y3YXUA%40mail.gmail.com.

[Jesse Glick]

On Wed, Sep 30, 2020 at 11:48 AM Tim Jacomb <timja...@gmail.com> wrote:
> I think that sometimes it resolves the wrong commit and triggers the master build

Indeed

https://ci.jenkins.io/job/Plugins/job/email-ext-plugin/job/master/107/

was supposed to have been on

https://ci.jenkins.io/job/Plugins/job/email-ext-plugin/job/PR-220/

[Tim Jacomb]

See my previous email (which was only sent to the infra mailing list) 

If it doesn’t get included in the email chain then:

https://groups.google.com/g/jenkins-infra/c/KkysaBSLs3A

On Thu, 1 Oct 2020 at 13:23, Francisco Robles <franro...@gmail.com> wrote:

Hi! I have been trying to re-run the failed check in this PR: https://github.com/jenkinsci/ec2-plugin/pull/493/checks?check_run_id=1179431212 (also in another one), I see a note saying "You have successfully requested Jenkins be rerun." but then in Jenkins there is nothing happening :(

Any idea why? I become a maintainer of the plugin some weeks ago and I am still getting in place :)

El jueves, 10 de septiembre de 2020 a las 0:15:00 UTC+2, tim.va...@gmail.com escribió:

Ah that also explains why I was seeing elements from warnings-ng (javadoc errors etc) appear in GH Checks, which I hadn't seen before. Cool.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CADN1OJ1P%3DsBCqE%2BYZNJbcEYNhnEwixK%3DasuN17A0T%3D6PXB86WA%40mail.gmail.com.

--


You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.


To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/37dd04cc-4308-4985-8e2a-44e4d0875b3en%40googlegroups.com.

[Xiong Kezhi]

The issue for the problem: https://github.com/jenkinsci/github-checks-plugin/issues/56

[Tim Jacomb]

Re running failed builds now fixed in 

https://github.com/jenkinsci/github-checks-plugin/releases/tag/v1.0.1

Only origin PRs worked previously, forks work now too.

Ci.Jenkins.Io is running the updated version

Thanks

Tim

You received this message because you are subscribed to the Google Groups "Jenkins Infrastructure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkins-infr...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/jenkins-infra/67beac6a-5e7b-48e3-9da4-f6b86dc74226n%40googlegroups.com.