Test on Java 21 #1324
Merged
Test on Java 21 #1324
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks like adding |
|
Note that this PR is not yet ready for review. |
|
Depends on jenkinsci/jenkins#8365 and jglick/simple-maven-project-with-tests#34. |
If we just need a repository with tests, we could replace Jesse's repo in favor of https://github.com/jenkinsci/hello-world-maven-builder, which is already used in another test case. |
|
@NotMyFault Note that this PR is not yet ready for review. |
timja
approved these changes
Aug 15, 2023
2 tasks
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Fixes #1320. I have retained a Java 11 build for the LTS line in order to alleviate concerns that we may accidentally begin to start relying on the behavior of newer Java versions in plugins. If this occurs, then shortly after the plugin is released its Java 11 tests would begin to fail on the LTS line (assuming the plugin does not require a weekly release, which is only the case for a small number of plugins). True, the plugin would have to be released to users before the issue is detected in this repository, but that is already a problem even today since there is no convenient way to run ATH or PCT from within a plugin PR build.