-
Notifications
You must be signed in to change notification settings - Fork 105
Test with Java 25 #481
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
Test with Java 25 #481
Conversation
Bumps [io.jenkins.tools.bom:bom-2.479.x](https://github.com/jenkinsci/bom) from 4023.va_eeb_b_4e45f07 to 5054.v620b_5d2b_d5e6. - [Release notes](https://github.com/jenkinsci/bom/releases) - [Commits](https://github.com/jenkinsci/bom/commits) --- updated-dependencies: - dependency-name: io.jenkins.tools.bom:bom-2.479.x dependency-version: 5054.v620b_5d2b_d5e6 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
…v620b_5d2b_d5e6' into test-with-java-25
Java 25 released September 16, 2025. The Jenkins project wants to support Java 25 soon. Compile and test on ci.jenkins.io with Java 25 and Java 21. Intentionally continues to generate Java 17 byte code as configured by the plugin parent pom. Does not compile or test with Java 17 on ci.jenkins.io any longer because we have found no issues in the past that were specific to the Java 17 compiler. The plan is to drop support for Java 17 in the not too distant future so that the Jenkins project is only supporting two major Java versions at a time, Java 21 and Java 25. Needs pull request: * jenkinsci#462 Testing done: * Confirmed that automated tests pass with Java 25 * Confirmed that DurableTaskStepTest fails on Fedora 43 with Java 21 and Java 25 * Confirmed that DurableTaskStepTest passes on Ubuntu 22.04 with Java 21 and Java 25
| <groupId>io.jenkins.tools.bom</groupId> | ||
| <artifactId>bom-${jenkins.baseline}.x</artifactId> | ||
| <version>4023.va_eeb_b_4e45f07</version> | ||
| <version>5054.v620b_5d2b_d5e6</version> |
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.
What is broken in the current version of the bom that this needed to be updated (the commit history is inverted)?
#482
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.
Nothing is broken in bom-2.479.x 4023.va_eeb_b_4e45f07. The tests pass on Ubuntu Linux with Java 25 and fail two tests on Fedora Linux 43 whether using bom-2.479.x 4023.va_eeb_b_4e45f07 or bom-2.479.x 5054.v620b_5d2b_d5e6. Since 5054.v620b_5d2b_d5e6 is the final BOM version for bom-2.479.x, it seemed reasonable to update to that version rather than remaining on a much older version, but that update is optional for this pull request.
I updated the plugin BOM in this pull request as an inadvertent result of the test failures on Fedora Linux 43 where I was doing my testing. It wasn't until after I had explored further that I realized the test failures are specific to Fedora Linux 43 (at least in my configuration). I can remove the BOM upgrade if that will allow the change to be 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.
if nothing is broken then #482 should suffice and we should be able to close this
|
Closing in favor of pull request: |
Test with Java 25
Java 25 released September 16, 2025. The Jenkins project wants to support Java 25 soon. Compile and test on ci.jenkins.io with Java 25 and Java 21.
Intentionally continues to generate Java 17 byte code as configured by the plugin parent pom.
Does not compile or test with Java 17 on ci.jenkins.io any longer because we have found no issues in the past that were specific to the Java 17 compiler. The plan is to drop support for Java 17 in the not too distant future so that the Jenkins project is only supporting two major Java versions at a time, Java 21 and Java 25.
Includes pull request:
Testing done
Submitter checklist
Link to relevant issues in GitHub or JiraLink to relevant pull requests, esp. upstream and downstream changes