Update Java versions and Debian version #746
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update Java versions and Debian version
Updates the base Debian version to the most recent release of Bookworm.
Updates the Java versions to the most recent releases of container images from the Eclipse Temurin container images:
New Java releases are currently being prepared by Eclipse Temurin. Their banner message says:
When they are available, the Java versions will need to be upgraded to:
Testing done
Ran
make build
successfully on my local Debian testing machine with Docker version 25.0.0, build e758fe5.Ran
make test
successfully on my local Debian testing machine with Docker version 25.0.0, build e758fe5.I've been actively using Java 11.0.21, Java 17.0.9, and Java 21.0.1 for various Jenkins controllers and Jenkins agents since their release 3 months ago. I've seen no issues reported in Jenkins Jira or in the various GitHub issues of the Jenkins project that are specific to those versions.
Submitter checklist