-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
Bump to latest 1.50 parent pom release #3783
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
Conversation
As 1.51 is upcoming, main goal here is to get an intermediate release with 1.50 in case we have data in case things go wrong with one or another and more quickly figure if this is likely to be coming from 1.50 or 1.51.
|
@daniel-beck @oleg-nenashev when/if the PR build is successful, I think it would be good to merge this before Monday so it gets in the next release. I'm aware it's very late, so I'm fine if you think this is too dangerous. I explained in the description that my intent here would be to get an intermediate release before we bump to upcoming 1.51, which I think would be better in case we have issues to diagnose. Thanks a lot |
|
|
|
BTW, last PR rebuild only fails on the |
|
Facepalm, now the unrelated failure comes from a new test added for security-904 iiuc. Groundhog day |
FTR: #3799 |





As 1.51 is upcoming (esp. to include the bump to extra-enforcer-rules to support JDK 11), the main goal here is to get an intermediate release with 1.50.
This way in case something goes wrong, it will be hopefully easier and quicker to figure where this comes from.
No JIRA, small enough.
Diff is jenkinsci/pom@jenkins-1.49...jenkins-1.50 (contains only the SUREFIRE-1588 workaround)
Proposed changelog entries
Internal:update to 1.50 parent pom to get the SUREFIRE-1588 workaround.Submitter checklist
- [ ] JIRA issue is well described* Use the
Internal:prefix if the change has no user-visible impact (API, test frameworks, etc.)Desired reviewers
@jglick given changes in 1.50 all come from him.