-
Epic
-
Resolution: Done
-
Major
-
4.13, 4.12, 4.14, 4.15
-
None
-
JDK 21 Upgrade
-
False
-
None
-
False
-
Not Selected
-
To Do
-
SECFLOWOTL-20 - Jenkins Java 11 EOL
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
Update Jenkins to use the next supported LTS JDK by default - JDK 21
Why is this important?
JDK 11 EOL is end of Q3 2024 - customers need time to test Jenkins with JDK 21.
JDK 21 is also available, and will be the next Java version with "extended" LTS support from the OpenJDK community (akin to Java 8).
Scenarios
- Run Jenkins with JDK 21
- Build Java apps with JDK 21
Acceptance Criteria (Mandatory)
- Jenkins uses JDK 21 by default
- Jenkins plugins compile with JDK 21
- Customers can downgrade the JDK to Java 11
Stretch/optional goal: allow the JDK to be upgraded to 21
Dependencies (internal and external)
TBD
Previous Work (Optional):
TBD
Open questions::
TBD
Done Checklist
- Acceptance criteria are met
- Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
- User Journey automation is delivered
- Support and SRE teams are provided with enough skills to support the feature in production environment
- is blocked by
-
JKNS-385 Jenkins 4.15 Release Stream
- Closed
- is depended on by
-
JKNS-410 Java 11 EOL
- To Do
-
JKNS-496 [4.16] Remove JDK 11 from Jenkins Images
- Closed
-
JKNS-497 [4.15] Remove JDK 11 from Jenkins Images
- Closed
-
JKNS-498 [4.14] Remove JDK 11 from Jenkins Images
- Closed
-
JKNS-499 [4.13] Remove JDK 11 from Jenkins Images
- Closed
-
JKNS-500 [4.12] Remove JDK 11 from Jenkins Images
- Closed
- is related to
-
JKNS-454 Openshift Login Plugin Produces Ambiguous Permissions
- Backlog