-
Notifications
You must be signed in to change notification settings - Fork 52
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
Init 2.375.1 #1561
Init 2.375.1 #1561
Conversation
@timja @NotMyFault this passed tests when for #1479 we needed to pin Line 17 in a688dc3
Line 588 in a688dc3
Line 567 in a688dc3
|
Thanks @jglick. There may be a related issue that needs a fix. The updatecli job on the master branch now expects that a 2.375.1 release exists. The GitHub reported status of the master branch shows that the master branch is failing because updatecli is failing to find the 2.375.1 release. The master branch on ci.jenkins.io is passing, but the updatecli GitHub action is failing. Will the failing updatecli GitHub action on the master branch prevent a release of a new version of the BOM? |
Or temporarily suppress Line 40 in 3163980
master to block releases which fail in intermediate lines, but this would add a lot of load to ci.jenkins.io. https://github.com/jenkinsci/pipeline-github-plugin#properties could be installed in which case we could check pullRequest.labels , which could also serve to replace Line 1 in 3163980
|
@MarkEWaite you will need to ask someone else to fix updatecli config, since I do not understand any of it. |
jenkinsci/bom#1561 (comment) discusses why we should assure that the bom is already testing the weekly that will be the baseline of the new LTS before we add a new LTS to the bom.
No description provided.