2025-04-08T16:00:00Z
Apr 8, 2025 - Latest Jenkins LTS, container updates
Attending:
- Mark Waite, Giovanni Vaccarino, Birajit Saikia, Kris Stern
Agenda
- Proposal: switch default containers (“latest” tags) to use Java 21
- Java 17 end of life warning is displayed to administrators since 31 Mar 2025
- Java 17 is end of life for Jenkins 31 Mar 2026
- jenkins/jenkins:latest has a warning that
- Need a help desk issue to track as a sub-issue of larger Java 21 transition
- Needs changes in
- Controller image - GitHub - jenkinsci/docker: Docker official jenkins repo - PR-2008
- SSH agent image - GitHub - jenkinsci/docker-ssh-agent: Docker image for Jenkins agents connected over SSH
- Inbound agent image - GitHub - jenkinsci/docker-agent: Jenkins agent (base image) and inbound agent Docker images
- Java 17 end of life warning is displayed to administrators since 31 Mar 2025
- End of support for Java 11/2.479.x
- Container repo for controller has dropped Java 11
- Weekly 2.463 dropped support for Java 11.
- Jenkins LTS 2.479.1 dropped support for Java 11 on 30 Oct 2024.
- Jenkins 2.479.3 has been released on 2.479.3 was on January 8, 2025
- Jenkins infra end of support for Java 11 needs planning and discussion
- Infra team is willing to continue Java 11 for a while, but at some point in the future, Java 11 won’t be available on Jenkins infra
- Plan is still being developed, no timelines have been set
- Endoflife.date could help monitor that - Eclipse Temurin 11 end of life October 2027
- Infra team is willing to continue Java 11 for a while, but at some point in the future, Java 11 won’t be available on Jenkins infra
- Unofficial campaign to update plugins to JDK11/17.
- Today is Oracle Patch Day - new Java version releases today
- 11.0.26, 17.0.15, 21.0.7
- About a week for Eclipse Temurin to be available
- Automation will detect when the new versions are ready for us to package
- Java 25
- Temurin supplies JDK 25 early access binaries
- The infra team is busy with other tasks which are more urgent
- We should create a task in the helpdesk nonetheless
- Use subtasks, to use it as a JIRA epic
- We should create a task in the helpdesk nonetheless
- We could nonetheless try to write an updatecli manifest and see if it works before proposing changes
- Which repositories should we target first?
- Infra
- Controller
- Agents?
- Which repositories should we target first?
- Why not create a cookbook (Kris and Bruno) in order to log what we had to go through?
- Kris created an issue in the jenkins.io issue tracker: Add documentation for Java migration cookbook · Issue #8002 · jenkins-infra/jenkins.io · GitHub