Test with Java 21 #109
Merged
Test with Java 21 #109
Conversation
This file contains hidden or 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
Bumps [io.jenkins.tools.bom:bom-2.361.x](https://github.com/jenkinsci/bom) from 2081.v85885a_d2e5c5 to 2102.v854b_fec19c92. - [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.361.x dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
Java 21 was released Sep 19, 2023. We want to announce full support for Java 21 in early October and would like the most used plugins to be compiled and tested with Java 21. The acceptance test harness and plugin bill of materials tests are already passing with Java 21. This is a further step to improve plugin readiness for use with Java 21 and for development with Java 21. The change intentionally tests only two Java configurations, Java 17 and Java 21 because we believe that the risk of a regression that only affects Java 11 is low. We generate Java 11 byte code with the Java 17 and the Java 21 builds, so we're already testing Java 11 byte code.
I still need to get back to work on jenkinsci/scm-api-plugin#180. Too much to do. |
Remove the old changelog and link to a tagged version on GitHub. Replace outdated jenkins-ci.org with jenkins.io domain name. Link bug reporting to a page that offers bug, improvement, and security reporting so that users are encouraged to report issues more accurately and are encouraged to report security issues in the SECURITY project rather than the JENKINS project.
auto-merge was automatically disabled
October 15, 2023 13:10
Head branch was pushed to by a user without write access
|
I pushed 3ff6a91 because I could not find a way to make ci.jenkins.io find the commits to build. It continued to report that the |
|
Tests are passing on ci.jenkins.io |
jglick
approved these changes
Oct 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Test with Java 21
Java 21 was released Sep 19, 2023. We want to announce full support for Java 21 in early October and would like the most used plugins to be compiled and tested with Java 21.
The acceptance test harness and plugin bill of materials tests are already passing with Java 21. This is a further step to improve plugin readiness for use with Java 21 and for development with Java 21.
The change intentionally tests only two Java configurations, Java 17 and Java 21 because we believe that the risk of a regression that only affects Java 11 is low. We generate Java 11 byte code with the Java 17 and the Java 21 builds, so we're already testing Java 11 byte code.
Supersedes pull request:
Testing done
Tests pass with Java 21 on Linux
Submitter checklist