1 min

Tags in this article

, , , ,

Jenkins, a DevOps tool for CI/CD, is making Java 11 mandatory from version 2.257 onwards. Java 11 will become a cornerstone of Jenkins’ future.

Until recently, the tool was primarily based on Java 8. Since the June release of version 2.257, Java 11 is mandatory. Java 8 remains fully usable and supported until 2030.

Jenkins’ developers explain that more and more third-party integration solutions are upgrading to Java 11. Without mandating Java 11, integrating and securing becomes increasingly difficult.

Furthermore, the developers appreciate Java 11’s performance and popularity. The version promises to attract more users, which strengthens the community.

More reasons

In its announcement, Jenkins addresses the imminent arrival of Java 17. Jenkins started supporting the version in a late-June release. However, according to the developers, support is in its infancy. Users that migrate directly from Java 8 to Java 17 may face issues. The developers indicate that migrating from Java 11 to Java 17 is preferable, laying out a guideline in their announcement.

Tip: Mirantis introduces DevOpsCare, a CI/CD solution for Kubernetes