Uploaded image for project: 'OpenShift Jenkins'
  1. OpenShift Jenkins
  2. JKNS-455

[4.15] Use JDK 21 by default

XMLWordPrintable

    • 1
    • False
    • None
    • False
    • SECFLOWOTL-20 - Jenkins Java 11 EOL
    • Builds Sprint #10, Builds Sprint #11, Builds Sprint #12

      Story (Required)

      As a plaform team trying to use Jenkins for my CI I want the OpenShift Jenkins distribution to use JDK 21 by default.

      <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>

      JDK 11 is EOL in October 2024. We need to provide a version with JDK 17 before then so customers can test it.

      Out of scope

      <Defines what is not included in this story>

      Remove Java 11 - see JKNS-410

      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 the Jenkins docker file to install JDK-21 i the build

      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 runs with JDK 21 by default.
      • Platform teams can fall back to using JDK 11.
      • Backport to 4.12 release stream

      Note: this story should be cloned for each Jenkins release stream we will support.

      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

            rh-ee-sabiswas Sayan Biswas
            adkaplan@redhat.com Adam Kaplan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: