Attending:
Agenda:
- 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.
- Container image updates for the Jenkins controller
- LTS
- 2.492.3-rc has been released last Thursday
- 2.492.3 should be released next week (April 2nd). Bruno Verachten is the release lead
- Weeklies (2.502 and 2.503)
Dependency updates
- Bump updatecli/updatecli-action from 2.78.1 to 2.79.0
- Bump ubi9/ubi to 9.5-1741850090 in /rhel/ubi9/hotspot
- Bump Debian Bookworm Linux Version to 20250317
- LTS
- Container image updates for Jenkins agents
- No new release for the SSH agent
- One new release for the docker-agent (3299.v0d0d06908537-1)
Dependency updates
- Bump the Jenkins remoting version to 3299.v0d0d06908537
- Bump updatecli/updatecli-action from 2.78.1 to 2.79.0
- Bump UBI9 version to 9.5-1741850090
- Work in progress on images:
- Controller:
- Docker-agent:
- Docker-ssh-agent:
- Windows Server 2025 images
- 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?
- RISC-V
- Asked to access a RISC-V board (Banana Pi F3) with a recent OS and Docker so we can progress on the assessment of Jenkins on RISC-V
Jenkins agents and controller run on RISC-V (Mango Pi MQ-Pro and MILKV Pioneer), but these boards don’t have Docker