Test with Java 25

[MarkEWaite]

Test with Java 25

Java 25 released September 16, 2025. Jenkins core (weekly) has supported Java 25 since Jenkins 2.534, Oct 28, 2025. Jenkins core (LTS) has supported Java 25 since 2.541.1, Jan 21, 2026. 90% of the 300 most popular plugins now compile and test with Java 25.

Compile and test on ci.jenkins.io with Java 25 and Java 21.

Testing done

• None. Rely on ci.jenkins.io

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did

[kinow]

Thank you @MarkEWaite ! Will merge if build succeeds 👍

[MarkEWaite]

Thank you @MarkEWaite ! Will merge if build succeeds 👍

Thanks! My apologies that I based the pull request on an outdated local copy of the master branch. I've updated to the most recent upstream branch.

[MarkEWaite]

Thank you @MarkEWaite ! Will merge if build succeeds 👍

A new build has been launched.

[kinow]

Thanks @MarkEWaite . I had a super quick glimpse at the error, and I guess it could be the same one I had yesterday with a newer version of Selenium, #924 (if it's indeed just a Selenium error).

[MarkEWaite]

That is a surprising test failure.

I have permission on ci.jenkins.io, so I replayed the master branch with the addition of Java 25. It passed in build 851. I've started build 852 with Java 25 as well.

However, it seems to fail consistently on the pull request build as shown by builds 4, 5, and 6.

[MarkEWaite]

Results are even more surprising. If I include Java 25 as the first configuration entry, it fails the test. If I include it as the second configuration entry, it passes the test. The first configuration is the one that reports coverage metrics. Maybe there is a timing dependency in the coverage instrumentation that is somehow exercised on Java 25 and not on Java 21?