-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot re-run failed builds #2738
Comments
Hello @basil , I don't have any "Re-Run" button on the three examples. cc @jglick @MarkEWaite @jtnord In order to diagnose, I'll need help to understand how GitHub behaves when someone clicks on the "Re-Run" button: is it expected to send a webhooks to Jenkins or send a request directly to the pipeline job? One good start to diagnose if it sends a webhooks, would be to check the Multi Branch events history: https://ci.jenkins.io/job/Core/job/jenkins/indexing/events |
System log has this in it: Likely related to jenkinsci/github-checks-plugin#226
|
Yes you need to have write access on the repo. |
Ping @basil does the fix works for you now that ci.jenkins.io has been updated and restarted? |
The unit tests weren't quite right -.-, fixing atm |
Works now |
Many thanks! |
Service
ci.jenkins.io
Summary
After clicking the "Re-Run" button for a failed Jenkins core PR in the GitHub UI, the GitHub UI reports "You have successfully requested Jenkins be rerun", but a re-run of the Jenkins job is not triggered on
ci.jenkins.io
.Reproduction steps
Steps to reproduce
Expected results
The Jenkins job should be re-run.
Actual results
No Jenkins job re-run is taking place, despite the message "You have successfully requested Jenkins be rerun" being printed earlier in GitHub.
The text was updated successfully, but these errors were encountered: