Skip to content

[JENKINS-40689] Java 11 Phase 4: Deprecate support for Java 8 #17749

Closed
57 of 57 issues completed
Closed

Description

@jenkins-infra-bot

Currently Jenkins does not support Java 9, but we may want to do it soon. I have created this EPIC to start aggregating issues reported by users.

Assumed that many of the components in Jenkins will need updates for Java 9 support. For example:

  • ASM 6.0 supports JDK 9 as of 23 Sep 2017
  • Jetty 9.4.8 supports JDK 9 as of 21 Nov 2017 (using ASM 6.0)

Change sources:


Originally reported by oleg_nenashev, imported from: Java 11 Phase 4: Deprecate support for Java 8
  • status: Resolved
  • priority: Major
  • component(s): core
  • label(s): java11
  • resolution: Fixed
  • resolved: 2022-02-28T20:49:20+00:00
  • votes: 23
  • watchers: 51
  • imported: 2025-11-24
Raw content of original issue

Currently Jenkins does not support Java 9, but we may want to do it soon. I have created this EPIC to start aggregating issues reported by users.

Assumed that many of the components in Jenkins will need updates for Java 9 support. For example:

  • ASM 6.0 supports JDK 9 as of 23 Sep 2017
  • Jetty 9.4.8 supports JDK 9 as of 21 Nov 2017 (using ASM 6.0)

Change sources:

Activity

  1. jenkins-infra-bot commented on Dec 27, 2016

    @jenkins-infra-bot
    Author
  2. jenkins-infra-bot commented on Oct 29, 2017

    @jenkins-infra-bot
    Author
    wombosvideo:
    • Original comment link
    • Raw content of original comment:

      Jenkins supports Java 9 on Debian if you install OracleJava8 by Webupd8 and replace the binary files with java 9 files from http://jdk.java.net/9/ (or at least it did)

       

      I do not recommend this as it gave me errors in the settings I was not able to resolve by myself. Additionally, I just tested this on a new server and it now says that the version is not supported which is the way it should be.

    Jenkins supports Java 9 on Debian if you install OracleJava8 by Webupd8 and replace the binary files with java 9 files from http://jdk.java.net/9/ (or at least it did)

     

    I do not recommend this as it gave me errors in the settings I was not able to resolve by myself. Additionally, I just tested this on a new server and it now says that the version is not supported which is the way it should be.

  3. jenkins-infra-bot commented on Apr 25, 2018

    @jenkins-infra-bot
    Author
    antgel:
    • Original comment link
    • Raw content of original comment:

      I went with sudo update-alternatives --config java.

    I went with sudo update-alternatives --config java.

  4. jenkins-infra-bot commented on Apr 26, 2018

    @jenkins-infra-bot
    Author
    cobexer:
    • Original comment link
    • Raw content of original comment:

      Is this planned to be fixed in time for the end of Java 8 support? See Oracle Java SE Support Roadmap: http://www.oracle.com/technetwork/java/eol-135779.html

      Copying: End of Public Updates for Oracle JDK 8 As outlined in the Oracle JDK Support Roadmap below, Oracle will not post further updates of Java SE 8 to its public download sites for commercial use after January 2019.

    Is this planned to be fixed in time for the end of Java 8 support?
    See Oracle Java SE Support Roadmap: http://www.oracle.com/technetwork/java/eol-135779.html

    Copying:
    End of Public Updates for Oracle JDK 8
    As outlined in the Oracle JDK Support Roadmap below, Oracle will not post further updates of Java SE 8 to its public download sites for commercial use after January 2019.

  5. jenkins-infra-bot commented on Apr 26, 2018

    @jenkins-infra-bot
    Author
    oleg_nenashev:
    • Original comment link
    • Raw content of original comment:

      cobexer in the community we do not ETA and roadmap for it right now. There are some changes happening in the background, and there is a general agreement that we should do it somehow. But the timing may differ.

      If the support does not get delivered by Jan 2019, using other JDK distributions may be a temporary solution if you need a Java update. Too early to talk about it now IMHO, the Java 8 EoL date may change again.

    cobexer in the community we do not ETA and roadmap for it right now.
    There are some changes happening in the background, and there is a general agreement that we should do it somehow. But the timing may differ.

    If the support does not get delivered by Jan 2019, using other JDK distributions may be a temporary solution if you need a Java update. Too early to talk about it now IMHO, the Java 8 EoL date may change again.

  6. jenkins-infra-bot commented on Apr 26, 2018

    @jenkins-infra-bot
    Author
    oleg_nenashev:
    • Original comment link
    • Raw content of original comment:

      Java 9 is EoL, so I have renamed ticket to Java 10. It does not change the scope much. Java 11, ehm, may be fun

    Java 9 is EoL, so I have renamed ticket to Java 10. It does not change the scope much. Java 11, ehm, may be fun

  7. jenkins-infra-bot commented on Apr 27, 2018

    @jenkins-infra-bot
    Author
    jasjuang:
    • Original comment link
    • Raw content of original comment:

      I just wanted to add that I ran into the same problem when upgrading our jenkins server to Ubuntu 18.04. antgel's solution `sudo update-alternatives --config java` solves it for me. For those who are interested, here is what happens after executing the command

      ```

      There are 2 choices for the alternative java (providing /usr/bin/java).

      Selection Path Priority Status ------------------------------------------------------------

      • 0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 auto mode 1 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 manual mode 2 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode

      ```

      After I switched back to java 8, and then `sudo service jenkins start` jenkins comes back to life again.

    I just wanted to add that I ran into the same problem when upgrading our jenkins server to Ubuntu 18.04. antgel's solution `sudo update-alternatives --config java` solves it for me. For those who are interested, here is what happens after executing the command

    ```

    There are 2 choices for the alternative java (providing /usr/bin/java).

    Selection Path Priority Status
    ------------------------------------------------------------

    • 0 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 auto mode
      1 /usr/lib/jvm/java-11-openjdk-amd64/bin/java 1101 manual mode
      2 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode

    ```

    After I switched back to java 8, and then `sudo service jenkins start` jenkins comes back to life again.

  8. jenkins-infra-bot commented on May 22, 2018

    @jenkins-infra-bot
    Author
    brunolaturner:
    • Original comment link
    • Raw content of original comment:

      > Java 9 is EoL, so I have renamed ticket to Java 10. It does not change the scope much. Java 11, ehm, may be fun

       

      Java 10 will also be EoL soon, in September 2018. On the other hand (Oracle's) Java 11 will be a 5-year Long Term Support version. 11 might be a better target version, instead of pursuing the current rabbit down the hole.

    > Java 9 is EoL, so I have renamed ticket to Java 10. It does not change the scope much. Java 11, ehm, may be fun

     

    Java 10 will also be EoL soon, in September 2018. On the other hand (Oracle's) Java 11 will be a 5-year Long Term Support version. 11 might be a better target version, instead of pursuing the current rabbit down the hole.

  9. jenkins-infra-bot commented on May 22, 2018

    @jenkins-infra-bot
    Author
    oleg_nenashev:
    • Original comment link
    • Raw content of original comment:

      > Java 10 will also be EoL soon, in September 2018. On the other hand (Oracle's) Java 11 will be a 5-year Long Term Support version. 11 might be a better target version, instead of pursuing the current rabbit down the hole.

      That's correct. We will definitely change the version when really start working on that seriously. Stay tuned

    > Java 10 will also be EoL soon, in September 2018. On the other hand (Oracle's) Java 11 will be a 5-year Long Term Support version. 11 might be a better target version, instead of pursuing the current rabbit down the hole.

    That's correct. We will definitely change the version when really start working on that seriously. Stay tuned

  10. jenkins-infra-bot commented on Jun 8, 2018

    @jenkins-infra-bot
    Author
    oleg_nenashev:
    • Original comment link
    • Raw content of original comment:

      After some consideration I created a separate EPIC for Java 11: JENKINS-51805 If some tasks here are not feasible for Java 11, we can just close them as "Won't fix"

    After some consideration I created a separate EPIC for Java 11: JENKINS-51805
    If some tasks here are not feasible for Java 11, we can just close them as "Won't fix"

  11. jenkins-infra-bot commented on Jun 11, 2018

    @jenkins-infra-bot
    Author
    oleg_nenashev:

    Just in case somebody is interested, we are going to have an online "Jenkins & Java 10" hackathon next week.
    Everybody is welcome to join, see https://jenkins.io/blog/2018/06/08/jenkins-java10-hackathon/

  12. jenkins-infra-bot commented on Oct 1, 2018

    @jenkins-infra-bot
    Author
    oleg_nenashev:

    Latest status update is here: https://docs.google.com/document/d/1nIz1STmwOVMJ3vx68m6Xc4pv2oEKDRdyeYUNI8zZJsg/edit#heading=h.1478tpp0nycs 

    We drive this story as a part of Platform Special Interest Group in Jenkins

  13. jenkins-infra-bot commented on Dec 13, 2018

    @jenkins-infra-bot
    Author
    oleg_nenashev:

    We have announced Java 11 support preview in 2.155+ : https://jenkins.io/blog/2018/12/14/java11-preview-availability/

    Any feedback will be appreciated

  14. jenkins-infra-bot commented on Mar 17, 2019

    @jenkins-infra-bot
    Author
    oleg_nenashev:

    Java 11 support has been officially released in Jenkins 2.164.1. https://jenkins.io/blog/2019/03/11/let-s-celebrate-java-11-support/ 

  15. jenkins-infra-bot commented on Feb 28, 2022

    @jenkins-infra-bot
    Author
    basil:
    • Original comment link
    • Raw content of original comment:

      Let's declare victory on this epic. I have moved any remaining tasks to a follow-up epic, JENKINS-67688.

    Let's declare victory on this epic. I have moved any remaining tasks to a follow-up epic, JENKINS-67688.

  16. 52 remaining items

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions