Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require Java 11, test with Java 21 #56

Merged
merged 5 commits into from
Dec 15, 2023

Conversation

MarkEWaite
Copy link
Contributor

Require Java 11, 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.

Replaces pull requests:

Testing done

Confirmed that tests pass with Java 21 on Linux.

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
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes

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.
@MarkEWaite
Copy link
Contributor Author

@ikedam I'd appreciate it very much if you would merge this pull request so that the plugin is tested regularly with Java 21. No need for a release, just a merge.

MarkEWaite added a commit to MarkEWaite/repository-permissions-updater that referenced this pull request Dec 15, 2023
jenkinsci/groovy-postbuild-plugin#56 is the pull
request that I would like to merge.

I use the groovy postbuild plugin in my test environment and would like to
assure that it is regularly built and tested with Java 21.  The proposed
pull request will close several other pending pull requests and simplify
the maintenance of the plugin.

@ikedam as the sole maintainer of the plugin, would you approve me being
added as a maintainer?

If there is no response from @ikedam, I'm happy to wait the two weeks
for the adoption request to be active.
@MarkEWaite MarkEWaite added the chore Reduces maintenance effort by changes not directly visible to users label Dec 15, 2023
@MarkEWaite MarkEWaite merged commit fa36218 into jenkinsci:master Dec 15, 2023
13 checks passed
@MarkEWaite MarkEWaite deleted the test-with-java-21 branch December 15, 2023 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Reduces maintenance effort by changes not directly visible to users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant