Jenkins Agents Phasing Out Windows Server 2019 Support: A Call for Modernization

Effective August 21, 2026, the Jenkins project has announced it will no longer deliver container images based on Windows Server 2019 for its inbound and SSH agents. This decision follows Jenkins core's earlier cessation of support for Windows Server 2019 container images in Jenkins 2.569 and 2.568.1. The project advises users currently running agents on Windows Server 2019 to either upgrade to newer versions, specifically Windows Server 2022 or Windows Server 2025, or to build and maintain their own custom agent images for Windows Server 2019. This move is partly influenced by the retirement of Windows Server 2019 from services like Azure Kubernetes Service (AKS) on March 1, 2026, which no longer provides new node images or security patches for that version. This announcement carries significant implications for organizations and DevOps teams heavily reliant on Jenkins for their CI/CD pipelines, particularly those with Windows-based build and test environments. Continuing to use unsupported Windows Server 2019 agent containers after the effective date will expose these environments to potential security vulnerabilities due to the lack of official security patches and updates. Furthermore, teams may encounter compatibility issues with newer Jenkins features or plugins, leading to pipeline failures and increased operational overhead. The need to either upgrade or manage custom images introduces a mandatory migration effort, which, if not planned carefully, can disrupt development workflows and delay software releases. This deprecation aligns with a broader industry trend where cloud providers and open-source projects regularly sunset older operating system versions to focus resources on more modern, secure, and performant platforms. The mention of Azure Kubernetes Service (AKS) retiring Windows Server 2019 earlier in the year highlights how platform dependencies often cascade, forcing downstream projects like Jenkins to adapt. This continuous evolution is critical for maintaining robust security postures, leveraging performance enhancements, and ensuring compatibility with contemporary software ecosystems. It underscores the dynamic nature of cloud-native development and the constant need for infrastructure modernization to keep pace with technological advancements and security best practices. Practitioners should immediately audit their Jenkins environments to identify any agents running on Windows Server 2019 container images. The most straightforward path for many will be to plan an upgrade to Windows Server 2022 or 2025. This involves assessing application compatibility with the newer OS, updating any custom scripts or configurations, and thoroughly testing the updated pipelines. For those with specific constraints preventing an immediate upgrade, building and maintaining custom Windows Server 2019 agent images becomes a necessary, albeit more resource-intensive, alternative. This option demands a clear strategy for security patching and dependency management. Teams should prioritize this migration to avoid technical debt, maintain security compliance, and ensure their CI/CD pipelines remain efficient and supported. This is an opportunity to review overall agent strategy, potentially exploring more cloud-native or ephemeral agent solutions.