[JENKINS-73253] Build and test with Java 21 #3953
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.
Build and test with Java 21
Jenkins will require Java 17 or newer in weekly releases beginning June 18, 2024. Jenkins has supported Java 21 for a long time. I've been using Java 21 for my local development work without any issue.
The upgrade to Spring Framework 6 will require at least Java 17. Let's move to Java 21 to prepare for the future.
JENKINS-67909 is the Jira epic that tracks the Java 11 end of life. JENKINS-73253 is the issue for this pull request
Reviewer checklist
$pluginId Developers
team hasAdmin
permissions while granting the access.@Wadeck
) in this pull request. If an email contact is changed, wait for approval from the security officer.There are IRC Bot commands for it.