I've come to the conclusion that there is no way to do this. You can't select Build Now from the Jenkins Infra CI build site (probably to protect against spam usage which is fair enough) and nor do you have this on Github. So you need to create a new "event" in the PR as described above.
Whilst it is really frustrating that the build has failed due to no fault of your own and that this causes a big red cross to appear, it was explained to me that these builds are meaningless and don't *actually* block your PR. You can ignore the result of the CI build and merge *if you feel it is safe*. What I would like, given this, is for Jenkins Infra CI builds to send back not a build failure but something like *build unstable* if that is possible and detect when a build failure is caused by a bad PR or by bad infrastructure. If a human can read the logs and determine this then surely it is possible to do automatically. Maybe that would be a happy middle ground between (what seems to be to me) 90% successful infrastructure builds and 10% failures unrelated to your PR. What I would do instead is run mvn clean install locally and confirm the build. And maybe a message to that effect would be good too. On Saturday, 5 October 2019 03:28:48 UTC+1, Gavin Mogan wrote: > > A lot of people is close the pr. Then wait like 30 seconds. And reopen it. > > On Fri., Oct. 4, 2019, 6:56 p.m. Mark Waite, <mark.e...@gmail.com > <javascript:>> wrote: > >> The simplest technique for me has been to use `git commit --amend` on the >> most recent commit, then force push that change to the repository. There >> is almost always something that I can improve about the last commit in a >> pull request. >> >> On Fri, Oct 4, 2019 at 7:45 PM Richard Bywater <ric...@bywater.nz >> <javascript:>> wrote: >> >>> Hi >>> >>> One of my pull requests failed on ci.jenkins.io due to what looks like >>> an infrastructure issue ( >>> https://ci.jenkins.io/job/Plugins/job/htmlpublisher-plugin/view/change-requests/job/PR-48/3/console >>> >>> ) >>> >>> Is there a way of getting it to re-run the build job on the PR as I >>> don't seem to have access to "Build Now" on the Jenkins infrastructure and >>> Github doesn't seem to have a "recheck" option either. >>> >>> Ideally I'd really love to not have to create a dummy commit to do it as >>> that doesn't really seem like a very good way of getting around the issue >>> of jobs that fail due to infrastructure issues. >>> >>> Thanks >>> Richard. >>> >>> -- >>> 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 jenkin...@googlegroups.com <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwfoQdE%3Dr03LTgqC9_0XvnhgnAVTC4kNPftE6n7jCPV40A%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwfoQdE%3Dr03LTgqC9_0XvnhgnAVTC4kNPftE6n7jCPV40A%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> >> >> -- >> Thanks! >> Mark Waite >> >> -- >> 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 jenkin...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEUqBFdHCmubyfkojveMs2Z4hsOXpk9SfU29-tYX%3D%2BJuw%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEUqBFdHCmubyfkojveMs2Z4hsOXpk9SfU29-tYX%3D%2BJuw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6eafa9bb-6f0e-4268-9438-1808080fcd3c%40googlegroups.com.
