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
ci.jenkins.io repository scan of jenkins.io repo fails with a stack trace #3617
Comments
Fixes hub4j#1671 https://community.jenkins.io/t/multibranch-pipline-fails-because-triage-enum-doesnt-exist/7800 reports that the TRIAGE permission is unknown to the GitHub api library. jenkins-infra/helpdesk#3617 reports that the MAINTAINER permission is unknown to the GitHub api library. This adds both the triage and the maintain permission to the enumeration so that new releases of the plugins depending on this library can be done to avoid the stack trace reported in jenkins-infra/helpdesk#3617 That stack trace includes: java.lang.IllegalArgumentException: No enum constant org.kohsuke.github.GHPermissionType.MAINTAIN Special thanks to @pierrebeitz for the test case with wiremock.
👋 Hey all. We're rolling back the changes that triggered this issue. Since this is a Given the reliance on this field, we're going to undo this change and freeze the base Apologies this broke you, and my appreciation to the folks who got this to our attention. |
Our sincere appreciation to you for your rapid response. Thanks for hosting the Jenkins project. |
@MarkEWaite is it ok to rollback the plugin to its mainline version then (on ci.jenkins.io) and close the issue? @hpsin many many thanks for your help, the communication and efficiency! |
Proceeding to reintsall the "non prerelease" plugin on ci.jenkins.io (that will trigger a controller restart) |
Thanks everyone! |
* hub4j#1671 Create a test demoing the issue * Add MAINTAIN and TRIAGE permissions to permission type Fixes hub4j#1671 https://community.jenkins.io/t/multibranch-pipline-fails-because-triage-enum-doesnt-exist/7800 reports that the TRIAGE permission is unknown to the GitHub api library. jenkins-infra/helpdesk#3617 reports that the MAINTAINER permission is unknown to the GitHub api library. This adds both the triage and the maintain permission to the enumeration so that new releases of the plugins depending on this library can be done to avoid the stack trace reported in jenkins-infra/helpdesk#3617 That stack trace includes: java.lang.IllegalArgumentException: No enum constant org.kohsuke.github.GHPermissionType.MAINTAIN Special thanks to @pierrebeitz for the test case with wiremock. * Avoid exceptions by returning an UNKNOWN enum as needed When GitHub adds a new permission, return UNKNOWN with less permission than NONE. --------- Co-authored-by: Pierre Beitz <pibeitz@gmail.com> Co-authored-by: Mark Waite <mark.earl.waite@gmail.com> Co-authored-by: Carroll Chiou <cchiou@cloudbees.com>
Service(s)
ci.jenkins.io
Summary
The CI jobs for the www.jenkins.io documentation site are not being run on ci.jenkins.io because the repository scan is failing with the following message:
Reproduction steps
The text was updated successfully, but these errors were encountered: