Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-55547

Change base image for Evergreen (move away from Alpine)

    • Evergreen - Milestone 2

      Problem

      OpenJDK has not provided yet a base Alpine image for JDK 11.
      And it's not going to happen
      https://twitter.com/mreinhold/status/1046862466204950529 (Mark Reinhold is Chief Architect of the Java Platform Group)

      It might happen for JDK 12, as written in that tweet, but it's a might.

      This means we current cannot upgrade the JDK currently set up from 8 to 11 without more than consistent efforts. And even if we achieve to do it, this is quite out of scope, and dangerous for users, for the Jenkins Project to actually offer an openjdk build on Alpine, given even the official OpenJDK image is not doing it!

      This is even more an issue because the JDK release cadence has accelerated. JDK 12 is already coming, and JDK 13 is expected in September 2019 (https://openjdk.java.net/projects/jdk/13/spec/).

      Acceptance Criteria/Expected

      • Evergreen should use a platform that makes upgrading the JDK a no-brainer (managing the build of the JDK for Alpine is not the mission of the Jenkins Project)

      Technical note

      The new target platform/base image is not defined yet. Some people argue for Debian, some Ubuntu, some Centos/Fedora. There will probably be some discussion about this at some later point.

          [JENKINS-55547] Change base image for Evergreen (move away from Alpine)

          Baptiste Mathus created issue -
          Baptiste Mathus made changes -
          Description Original: h3. Problem

          OpenJDK has not provided yet a base Alpine image for JDK 11.
          And apparently, it's not going to happen
          https://twitter.com/mreinhold/status/1046862466204950529 (Mark Reinhold is Chief Architect of the Java Platform Group)

          It _might_ happen for JDK 12, as written in that tweet, but it's a _might_.

          This means we current **cannot** upgrade the JDK currently set up from 8 to 11 without more than consistent efforts. And even if we achieve to do, this seems quite out of scope, and dangerous for users, for the Jenkins Project to actually offer an openjdk build on Alpine, given even the official OpenJDK image is not doing it!

          This is even more an issue because the JDK release cadence has accelerated. JDK 12 is already coming, and JDK 13 is expected in September 2019 (https://openjdk.java.net/projects/jdk/13/spec/).

          h3. Acceptance Criteria/Expected

          * Evergreen should use a platform that makes upgrading the JDK a no-brainer (managing the build of the JDK for Alpine is not the mission of the Jenkins Project)

          h3. Technical note

          The new target platform/base image is not defined yet. Some people argue for Debian, some Ubuntu, some Centos/Fedora. There will probably be some discussion about this at some later point.
          New: h3. Problem

          OpenJDK has not provided yet a base Alpine image for JDK 11.
          And it's not going to happen
          https://twitter.com/mreinhold/status/1046862466204950529 (Mark Reinhold is Chief Architect of the Java Platform Group)

          It _might_ happen for JDK 12, as written in that tweet, but it's a _might_.

          This means we current **cannot** upgrade the JDK currently set up from 8 to 11 without more than consistent efforts. And even if we achieve to do, this seems quite out of scope, and dangerous for users, for the Jenkins Project to actually offer an openjdk build on Alpine, given even the official OpenJDK image is not doing it!

          This is even more an issue because the JDK release cadence has accelerated. JDK 12 is already coming, and JDK 13 is expected in September 2019 (https://openjdk.java.net/projects/jdk/13/spec/).

          h3. Acceptance Criteria/Expected

          * Evergreen should use a platform that makes upgrading the JDK a no-brainer (managing the build of the JDK for Alpine is not the mission of the Jenkins Project)

          h3. Technical note

          The new target platform/base image is not defined yet. Some people argue for Debian, some Ubuntu, some Centos/Fedora. There will probably be some discussion about this at some later point.
          Baptiste Mathus made changes -
          Description Original: h3. Problem

          OpenJDK has not provided yet a base Alpine image for JDK 11.
          And it's not going to happen
          https://twitter.com/mreinhold/status/1046862466204950529 (Mark Reinhold is Chief Architect of the Java Platform Group)

          It _might_ happen for JDK 12, as written in that tweet, but it's a _might_.

          This means we current **cannot** upgrade the JDK currently set up from 8 to 11 without more than consistent efforts. And even if we achieve to do, this seems quite out of scope, and dangerous for users, for the Jenkins Project to actually offer an openjdk build on Alpine, given even the official OpenJDK image is not doing it!

          This is even more an issue because the JDK release cadence has accelerated. JDK 12 is already coming, and JDK 13 is expected in September 2019 (https://openjdk.java.net/projects/jdk/13/spec/).

          h3. Acceptance Criteria/Expected

          * Evergreen should use a platform that makes upgrading the JDK a no-brainer (managing the build of the JDK for Alpine is not the mission of the Jenkins Project)

          h3. Technical note

          The new target platform/base image is not defined yet. Some people argue for Debian, some Ubuntu, some Centos/Fedora. There will probably be some discussion about this at some later point.
          New: h3. Problem

          OpenJDK has not provided yet a base Alpine image for JDK 11.
          And it's not going to happen
          https://twitter.com/mreinhold/status/1046862466204950529 (Mark Reinhold is Chief Architect of the Java Platform Group)

          It _might_ happen for JDK 12, as written in that tweet, but it's a _might_.

          This means we current *cannot* upgrade the JDK currently set up from 8 to 11 without more than consistent efforts. And even if we achieve to do it, this is quite out of scope, and dangerous for users, for the Jenkins Project to actually offer an openjdk build on Alpine, given even the official OpenJDK image is not doing it!

          This is even more an issue because the JDK release cadence has accelerated. JDK 12 is already coming, and JDK 13 is expected in September 2019 (https://openjdk.java.net/projects/jdk/13/spec/).

          h3. Acceptance Criteria/Expected

          * Evergreen should use a platform that makes upgrading the JDK a no-brainer (managing the build of the JDK for Alpine is not the mission of the Jenkins Project)

          h3. Technical note

          The new target platform/base image is not defined yet. Some people argue for Debian, some Ubuntu, some Centos/Fedora. There will probably be some discussion about this at some later point.
          Baptiste Mathus made changes -
          Labels Original: java11 New: java11 triaged
          Baptiste Mathus made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Baptiste Mathus made changes -
          Labels Original: java11 triaged New: evergreen java11 triaged
          Baptiste Mathus made changes -
          Sprint New: Evergreen - Milestone 2 [ 516 ]
          Baptiste Mathus made changes -
          Epic Link New: JENKINS-51805 [ 191255 ]
          Baptiste Mathus made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Baptiste Mathus made changes -
          Remote Link New: This issue links to "PR (Web Link)" [ 22300 ]
          Baptiste Mathus made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]

            batmat Baptiste Mathus
            batmat Baptiste Mathus
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: