-
Notifications
You must be signed in to change notification settings - Fork 38
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
Unable to re-request Github check via Github following upgrade from 1.0.16 to 1.0.18 #253
Comments
Interesting, the workaround isn't hard though, push a new commit / re-run the build once via Jenkins? Contribution welcomed though if someone wants to PR it. Will close in a month or so if no fix as the stale jobs will naturally go away |
Facing the same issue. I understand the effort constraints, but please consider this a serious problem, because this leads people to mistakenly believe that they have actually re-requested a Check Run. How is it possible that people may be tricked to believe so? Because every time "Re-run" is clicked, GitHub will show a blue banner that says,
and we can't expect all contributors to all repos using GitHub Checks Plugin to understand how Jenkins work with GitHub and realize that they have to distrust GitHub and check Jenkins for themselves. Hence, regarding this statement,
I would say this: It's not about whether the workaround is hard or easy; it's about whether making people realize that they have to distrust a platform that they have trusted for a long while (in our case, GitHub) is hard or easy. In a way, this bug is getting serious because it undermines trust. It's about psychology; It's about thinking in non-Jenkins-savvy developers' shoes. Thanks for your consideration. |
When github-checks-plugin doesn't find the build that it should restart, it logs a warning: github-checks-plugin/src/main/java/io/jenkins/plugins/checks/github/CheckRunGHEventSubscriber.java Lines 130 to 131 in c98fc7b
Is there a response that Jenkins could return to GitHub in this situation, to prevent GitHub from claiming "You have successfully requested [check name here] be rerun"? GitHub |
So I understand if this is the same issue, are you upgrading from the ~2.5 year old version to a more recent one now and you've got a builds that won't re-trigger because the previous check has the old ID? |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Controller is running Ubuntu Linux 18.04.
Github is GitHub Enterprise Server 3.2.6.
Reproduction steps
Expected Results
The check run is re-executed by Jenkins.
Actual Results
No check run is executed by Jenkins.
Anything else?
This appears to have been caused by this change: c686ef4
The "external_id" format used has changed from Jenkins "Job" to Jenkins "Run", in the case of "stale" external_id references in Github, older "Job" ID format is not accepted and generates the exception shown below:
The text was updated successfully, but these errors were encountered: