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

Java 11 EOL

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • 4.13, 4.12, 4.14, 4.15, 4.16
    • jenkins-agent-base, jenkins-server
    • None
    • Java 11 EOL
    • False
    • None
    • False
    • Not Selected
    • To Do
    • SECFLOWOTL-20 - Jenkins Java 11 EOL
    • 0% To Do, 10% In Progress, 90% Done

      Epic Goal

      Remove Java 11 from our Jenkins image once it is EOL from Red Hat

      This is a breaking change!

      Why is this important?

      Java 11 is EOL in October 2024. This means the packages will no longer receive security advisories or bug fixes from Red Hat.

      Scenarios

      TBD

      Acceptance Criteria (Mandatory)

      • JDK 11 cannot be used to run Jenkins
      • Prior Jenkins images that use JDK 11 must be marked as "Deprecated" in the Red Hat container catalog.

      Dependencies (internal and external)

      1. JKNS-409: Upgrade JDK to 17

      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

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

                Created:
                Updated: