You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should start using this LTS line as the default for all Windows builds everywhere (Azure agents, AWS agents), except for specific Docker builds
The depreciation of Windows Server 2019 and eventually 2022 are NOT part of this issue.
This new version brings a new feature that could help us for the Windows build performances: Dev Drive which allows creating a drive dedicated for the build files requiring a lot of I/Os (Maven local repository, build directories, etc.)
Task list (can be updated):
Add support for 2025 on Azure packer-images
Add support for 2025 on AWS packer-images
Deploy for ci.jenkins.io (AWS, and a bunch of labels to manage)
Test on a plugin build
Test on a Jenkins Core build
Test on all Docker image builds
Deploy for trusted.jenkins.io (Azure and a few labels)
Test on all Docker image builds
Deploy for cert.jenkins.io (Azure and a few labels)
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
The depreciation of Windows Server 2019 and eventually 2022 are NOT part of this issue.
This new version brings a new feature that could help us for the Windows build performances: Dev Drive which allows creating a drive dedicated for the build files requiring a lot of I/Os (Maven local repository, build directories, etc.)
Task list (can be updated):
EDIT:
Updated plan:
Support for Windows Server 2025 agents:
Details