-
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
[JENKINS-58770] Manage all BOM lines in one Git branch #107
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aw yeah. Good to go once the build is stabilized
Seem to be having CI failures with no clear cause, just Remoting errors. @oleg-nenashev do you have sufficient permissions to investigate? |
…kins.io is going to behave better today.
Opened #109 to investigate CI issues. Might suffice to just run PCT on the oldest and newest LTS lines, under the assumption that most errors reproducible in any line would also be reproducible in at least one of those…but so far in #109 it seems that even that would not suffice to get a complete build. |
JENKINS-58770. Getting ready for 2.190.1 + 2.176.4. Once released, I would go searching for existing BOM consumers and file PRs to switch to the new artifact name.