Java 8 is abandoned: Jenkins announces support for Java 11 and above only
Java 8 is abandoned: Jenkins announces support for Java 11 and above only.
Open Source Devops Tool Jenkins Announces : Starting with the June 28 release of Jenkins 2.357 and the upcoming September LTS release, Jenkins requires a minimum of Java 11.
Jenkins, originally known as Hudson, is an established continuous integration tool that has been in existence for more than a decade.
Since its inception in 2005, the Jenkins project has undergone several Java migrations.
The current migration from Java 8 to Java 11 is consistent with the migration history in the Jenkins project.
Developer Basil Crow explained in a blog post: The Jenkins project will likely stay on Java 8 in the short term, but doing so will do more harm than good for several reasons.
First, many of the key third-party libraries used by the Jenkins project (eg, Jetty, JGit, Spring Framework, and Spring Security) began to require newer versions of Java, and staying on Java 8 prevented the Jenkins project from receiving security updates from upstream projects.
In addition, the new version of Jaba brings significant runtime improvements to the Java platform.
For example, LinkedIn saw significant performance improvements when migrating to Java 11, while Adoptium saw significant memory usage improvements when migrating to Java 11 (same on Jenkins), and the recent Java runtime provides Many improvements to garbage collection.
Finally, keeping Java at the current version helps Jenkins attract and retain developers.
Currently, the official Jenkins Docker image has been based on Java 11 for several months, Java 8 is temporarily available as an alternative, and Java 17 is available in preview mode. But starting with Jenkins 2.357, the Java 8 image will be phased out, and the Java 17 image will transition from preview to general availability (GA).
In fact, the Jenkins team recommends that users use Java 17:
Jenkins support for Java 17 is brand new, although it has not yet reached the stage of general adoption within the Jenkins community.
Nonetheless, our experience is that Java 17 is a more reliable choice than Java 11, and we can confidently say that migrating from Java 11 to Java 17 will not be as painful as migrating from Java 8 to Java 11.