Jenkins Deprecates Windows Server 2019 Container Agents, Forcing CI Infrastructure Upgrades

The Jenkins project has officially reached end of life for container images based on Windows Server 2019 across its inbound agent and SSH agent ecosystems, effective August 21, 2026. This move follows the prior removal of Windows Server 2019 container support in Jenkins core releases (2.569 and LTS 2.568.1). Moving forward, the Jenkins Platform Special Interest Group will exclusively deliver Windows container images based on modern operating system releases, specifically Windows Server 2022 and Windows Server 2025. For DevOps and infrastructure teams, this retirement carries direct operational urgency. In containerized continuous integration environments, agent images form the execution fabric for compiling code, running tests, and assembling release artifacts. Unmaintained agent baselines no longer receive critical security patches, toolchain compatibility fixes, or runtime updates. Teams supporting legacy .NET Framework applications, C++ compilers, or Windows-specific automated pipelines will experience broken dynamic agent scaling and mounting security non-compliance if they attempt to pull upstream images that are no longer published or refreshed. This decision reflects a broader, industry-wide shift toward deprecating legacy Windows container infrastructure. Major managed Kubernetes services, including Azure Kubernetes Service (AKS), retired Windows Server 2019 support earlier this year to focus on the performance and security capabilities of newer Windows Server releases. As container runtimes and Kubernetes orchestrators advance, sustaining multiple historical Windows kernel versions imposes substantial maintenance debt on open-source maintainers due to Windows container host-process isolation requirements. In practice, platform administrators must evaluate their agent pools immediately. Organizations have two primary remediation paths: upgrading their container hosts and build agent definitions to Windows Server 2022 or Windows Server 2025, or taking on the operational responsibility of authoring and hosting custom Windows Server 2019 base images internally. The recommended long-term path is upgrading host infrastructure to modern OS releases, which improves container start times, reduces image footprints, and ensures compatibility with current Jenkins agent protocols.