Repository navigation
[JENKINS-67908] Java 17 Phase 1: Support Java 17 #17899
Description
Add support for Java 17 in preview form while continuing to support and recommend Java 11.
The most common issue is mixing mocks with JenkinsRule-based integration tests, resolved by either reducing the use of mocks (thereby turning the test into a pure integration test) as was done in JENKINS-68025, or increasing the use of mocks (thereby turning the test into a pure unit test) as was done in JENKINS-69353.
Originally reported by basil, imported from: Java 17 Phase 1: Support Java 17
- status: Open
- priority: Major
- component(s): core
- label(s): java17
- resolution: Unresolved
- votes: 4
- watchers: 9
- imported: 2025-11-24
Raw content of original issue
Add support for Java 17 in preview form while continuing to support and recommend Java 11.
The most common issue is mixing mocks with JenkinsRule-based integration tests, resolved by either reducing the use of mocks (thereby turning the test into a pure integration test) as was done in
JENKINS-68025, or increasing the use of mocks (thereby turning the test into a pure unit test) as was done inJENKINS-69353.
Activity
jenkins-infra-bot commentedon Jun 29, 2022
Raw content of original comment:
How can I run jenkins 2.357 on systemd? I just change the JAVA_HOME environment variable from /opt/jdk11 to /opt/jdk17 but the service failed.
I am using Adoptium Semeru distribution (Open J9) on both versions (11 and 17)
jenkins-infra-bot commentedon Jun 29, 2022
basil:
Raw content of original comment:
acrespo This is not a support site; please use the users mailing list or community forum for this kind of question.
jenkins-infra-bot commentedon Sep 14, 2022
basil:
Raw content of original comment:
AtomicBooleanon Java 17 x-stream/xstream#308)Here are the types that I have observed to be problematic with XStream on Java 17:
AtomicBooleanon Java 17 x-stream/xstream#308)