-
Notifications
You must be signed in to change notification settings - Fork 251
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
Update plugin BOM and jenkins version #502
Conversation
Let's see if just updating the parent POM as in #503 (ignoring the BOM update and version bump) is sufficient to keep the tests stable and for my Java 17 work. |
I am currently testing on my local windows env to see if I can reproduce edit: am able to reproduce locally |
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.
Build failed. Suggest closing this PR in favor of #503.
Looks like enable |
going to keep this PR open to see if we can resolve the BOM bump issues |
Hmm, seems like #503 should have caused some of those to be automatically closed? 👀 |
// longpaths to support longer filenames for windows. Only needs to be set once. | ||
otherRepo.git("config", "--global", "core.longpaths", "true"); |
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.
Can be reverted now that jenkins-infra/pipeline-library#334 is merged?
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.
Filed #506
This PR refiles the BOM portion of #498 as it was reverted in #501 due to windows CI failures.
Failures generated are
filename too long
. See: https://github.com/jenkinsci/pipeline-model-definition-plugin/runs/5580211853See also: #499
cc @basil