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

Test with Java 21 #230

Merged
merged 1 commit into from
Nov 13, 2023
Merged

Test with Java 21 #230

merged 1 commit into from
Nov 13, 2023

Conversation

MarkEWaite
Copy link
Contributor

Test with Java 21

Java 21 was released Sep 19, 2023. We want to announce full support for Java 21 in November 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 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.

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
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

Java 21 was released Sep 19, 2023. We want to announce full support for
Java 21 in November 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 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.
Copy link

codecov bot commented Nov 4, 2023

Codecov Report

Merging #230 (add6072) into main (1c45aa5) will increase coverage by 50.00%.
Report is 2 commits behind head on main.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main     #230       +/-   ##
===========================================
+ Coverage        0   50.00%   +50.00%     
- Complexity      0       17       +17     
===========================================
  Files           0        3        +3     
  Lines           0       76       +76     
  Branches        0        5        +5     
===========================================
+ Hits            0       38       +38     
- Misses          0       31       +31     
- Partials        0        7        +7     

see 3 files with indirect coverage changes

📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!

@uhafner uhafner added the internal Internal changes without user or API impact label Nov 13, 2023
@uhafner uhafner merged commit b5af2b0 into jenkinsci:main Nov 13, 2023
26 of 27 checks passed
@MarkEWaite MarkEWaite deleted the test-with-java-21 branch November 13, 2023 22:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Internal changes without user or API impact
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants