Jenkins Sunsets Windows Server 2019 Agent Container Support

Effective August 21, 2026, the Jenkins project has announced the end of support for Windows Server 2019 container images for its inbound agent and SSH agent images. This means that Jenkins will no longer deliver official container images based on Windows Server 2019. The project had previously stopped supporting Windows Server 2019 container images in Jenkins core versions 2.569 and 2.568.1. This end-of-life (EOL) announcement carries significant implications for organizations that rely on Jenkins for their CI/CD pipelines, particularly those with a substantial investment in Windows-based build environments. For practitioners, the immediate concern is ensuring that their Jenkins agents remain on supported platforms to receive security patches, bug fixes, and access to the latest features. Running unsupported software introduces considerable security risks and can lead to compliance issues. Furthermore, it can hinder the adoption of newer Jenkins capabilities that might depend on more modern underlying infrastructure. This change directly impacts build engineers, DevOps teams, and infrastructure administrators responsible for maintaining Jenkins deployments. This move by the Jenkins project aligns with a broader industry trend of accelerating deprecation cycles for older operating system versions and container runtimes. Cloud providers and open-source projects alike are increasingly pushing users towards more current, secure, and performant platforms. For instance, major cloud vendors frequently update their base images and recommend migrating off older versions to leverage performance improvements and enhanced security features. This continuous evolution is critical in the fast-paced world of CI/CD, where the underlying infrastructure must keep pace with rapid software development and deployment cycles. The shift also reflects the growing maturity and adoption of containerization, where maintaining a lean and up-to-date image footprint is a best practice for efficiency and security. DevOps teams and Jenkins administrators should immediately inventory their existing Jenkins agent deployments to identify any instances running on Windows Server 2019 container images. The primary action item is to plan and execute a migration strategy to a supported Windows Server version, such as Windows Server 2022, for their Jenkins agents. This migration should include thorough testing of existing pipelines on the new environment to preempt any compatibility issues. Practitioners should also consider automating the lifecycle management of their agent images to ensure they stay current with future EOL announcements. Failure to migrate will result in increased operational risk due to lack of security updates and potential incompatibility with future Jenkins core and plugin updates. This is an opportune moment to evaluate the overall agent strategy, potentially exploring more cloud-native or ephemeral agent solutions to reduce the burden of OS-level maintenance.