Switch controllers to use Windows 2025 agents by default #4955
Description
Extracted from #4791 (comment)
What this issue is about
Windows 2025 Server is the current (and most recent) LTS line.
As per https://learn.microsoft.com/en-us/windows/release-health/windows-server-release-info, it has been released since November 2024 and will be supported until November 2029.
We should start using this LTS line as the default for all Windows builds everywhere (Azure agents, AWS agents), except for specific Docker builds
Agent template labels to take in account
In order of frequency, here are the usually requested agent labels for Windows builds in Jenkins ecosystem:
buildPlugin:
- docker-windows
- maven-17-windows
- maven-21-windows
- maven-25-windows
- maven-17-windows-nonspot
- maven-21-windows-nonspot
- maven-25-windows-nonspot
Core:
- maven-17-windows
- maven-21-windows
- maven-25-windows
- maven-17-windows-nonspot
- maven-21-windows-nonspot
- maven-25-windows-nonspot
Docker images:
- windows-2019
- windows-2022
- windows-2025
Others:
- ATH, BOM, UC: No Windows build.
- trusted.ci.jenkins.io: Windows is only used for docker image publication
- Jobs using the same set of agent template labels on both ci.jenkins.io and trusted.ci.jenkins.io
- release.ci.jenkins.io: Windows is only used for packaging via Kubernetes cloud agents
- Out of scope as blocked by AKS on Windows 2022 for now, cf Add support for Windows 2025 agents #4791 (comment)
- infra.ci.jenkins.io: Windows is not used.
- cert.ci.jenkins.io:
- maven-17-windows
- maven-21-windows
- maven-25-windows
Plan
Switch controllers to use Windows 2025 agents by default
- Ensure labels defined above correspond to Windows 2025 agent template definitions
- With the addition of missing JDK templates if needed
- The switch to JDK25 by default will be done with Use JDK25 for our Jenkins controllers #4941
- On ci.jenkins.io:
maven-<jdk>-windows,maven-<jdk>-windows-nonspot&docker-windows- Prepare PR
- Announce on jenkinsci-dev mailing list: https://groups.google.com/g/jenkinsci-dev/c/lEM0c9e_-LA
- Merge templates one hour later
- On cert.ci.jenkins.io,
maven-<jdk>-windows
Note: on trusted.ci.jenkins.io jobs only use specific windows-<version> labels, nothing to do.
Definition of done
Acceptance tests on the 2 updated controllers show that these labels are spawning Windows 2025 agents as expected:
- docker-windows
- maven-17-windows
- maven-21-windows
- maven-25-windows
- maven-17-windows-nonspot
- maven-21-windows-nonspot
- maven-25-windows-nonspot
Results: