Story (Required)

As a platform team trying to use Jenkins for CI I want the OpenShift Jenkins plugins to work with JDK 17

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

Java 11 is EOL in October 2024. We need the Jenkins plugins to work with JDK 21.

Out of scope

<Defines what is not included in this story>

• Use JDK 21 when running the Jenkins images themselves. See JKNS-455

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Update builder image to include JDK21.

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

TBD

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

• Jenkins plugins compile upstream with JDK 21
• Jenkins plugins compile downstream with JDK 21

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met