2026-06-09T11:30:00Z
Jun 9, 2026
Attending: Mark Waite, Damien Duportal, Herve Le Meur
Agenda
- Java 25
- 240 of the top 250 active plugin repositories are building and testing with Java 25
- LTS updates
- New LTS baseline: 2.555
- Next baseline likely 2.568
- Spring Security 7 and Spring Framework 7 - Mark Waite
- In weekly 2.556 and later, no issues reported
- LTS in July 2026
- Spring Security 6.x end of support is June 30, 2026
- Spring Framework 7.0.8 and 6.2.19 released June 8, 2026 with fixes for 18 CVEs
- Refer to release announcement and blog post
- Spring Framework 6.2.19 is the last public release of Spring 6
- Discussion with the security team if Jenkins 2.555.4 release is needed to include Spring Framework
- Container image updates for the Jenkins controller
- New releases with regular updates to operating system versions
- Add environment variable substitution for reference configuration files
- Deprecation and archival of jenkinsci/docker-inbound-agents
- Repository archived
- Work in progress on images:
- Drop Windows 2019 support - in progress (infra)
- Jenkins infra team recommends that we stop using Windows 2019 containers
- Painful to maintain a Windows 2019 with Windows 2022 and Windows 2025
- Not supported in Azure for container images
- Extended support for virtual machines (only security patches)
- Risk that AWS might stop publishing new 2019 versions
- Stop providing controller images and agent images
- Windows container proposals
- 2.555.3 the last LTS to provide a controller image
- Drop it in the weekly release
- Add it as an issue and blog posts
- Blog post 1 - drop all Windows 2019 container images (controllers and agents)
- Blog post 2 - announce end of life of all Windows contains images for controllers
- What about Windows agent container images?
- Users running Jenkins controller in a Windows container must upgrade to Windows 2022 or build their own image or use the native (MSI) installation
- Mark has seen no bug reports of Windows controller container images, drop Windows 2019 immediately, consider dropping all Windows completely
- Only know of 1 user of controller on Windows containers
- Migration paths for Jenkins container agents on Windows Server
- Build your own container image from our Dockerfile, maintain it yourself, store it yourself
- Create your own Dockerfile
- Run agent without a Docker container
- Jenkins infra team recommends that we stop using Windows 2019 containers
- Support for Windows container agents
- Retain them for now because there are some use cases
- Docker Pipeline plugin allows Windows containers as agents
- Helpdesk Windows 2025 ticket is closed
- Optimize cost and maintenance by merging Windows 2022 and Windows 2025 templates - pending infra team bandwidth
- Retain them for now because there are some use cases
- Controller:
- Windows Nanoserver images are becoming more difficult to build
- PowerShell is not provided in a standard nanoserver image
- Nanoserver and PowerShell release process has changed
- May consider dropping Nanoserver, after we review Microsoft’s policy
- PowerShell is not provided in a standard nanoserver image
- Docker-agent:
- chore(windows): build from Windows 2025 agents by default - more work needed to build older images on new OS
- chore(windows): run each JDK tests in parallel
- Docker-ssh-agent:
- Drop Windows 2019 support - in progress (infra)