Being able to do this via a comment is a recent addition and already makes it much easier and faster.
I have added 'please run jobs' as a reply template in github, making it even faster.
Starting a build automatically would be nice. But this only works when this is a change in one package without related and needed changes in other packages. When PRs in multiple packages belong together, it is useless and wasteful to start Jenkins jobs on the individual PRs.
Especially on sprints this would be unworkable.
Were you logged in? Build buttons are only visible to authenticated users. You can login with your github account.
Full info is on github. There might be a link to that somewhere in a logical spot, but I don't immediately see it. Currently, the main PR job page at least says this in the center top: "To trigger a job, just login with your GitHub account and provide the pull request URL."
Easiest is to login, go to the failing job, and click the Rebuild button. This will show a form with the PR url (or multiple urls) already filled in.
Someone has to. I finally made several robot tests more robust yesterday. When there are unrelated failures you have several options:
- Fix the tests, possibly in a separate PR in a separate package.
- Restart the failing job and hope it works now.
- Add a comment on your PR saying that you think the failures are unrelated and that you think it is ready for merge after all.
You can do this yourself, or wait for someone else to step in. Doing it yourself takes more time for you, but may get your PR merged faster.