Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Component/s: ci.jenkins.io, trusted.ci, windows
-
Labels:None
-
Similar Issues:
Description
More information here
Windows Server 1903 end of life is December 2020. Our windows infrastructure should be upgraded to the latest version available 1909 on both Azure and AWS.
1) We need to provide new packer images for windows 1909 in jenkins-infra/packer-images
2) Update windows agent on ci.jenkins.io and trusted.ci
Attachments
Activity
https://github.com/jenkins-infra/packer-images/pull/44 adds the ability to verify that docker images can be built correctly during the packer build
Gareth Evans
added a comment - https://github.com/jenkins-infra/packer-images/pull/44 adds the ability to verify that docker images can be built correctly during the packer build Latest Update
Windows Docker images need to build on exactly the same kernel version as the host.
This means that, if we update the host, we need to update https://github.com/jenkinsci/docker/blob/master/8/windows/windowsservercore-1809/openj9/Dockerfile#L2 (and all other assorted builds) - this needs to be done at the same time that the new base images are deployed.
We could tag the VMs with `1909`/`1809` and support both builds for a period of time? But we’re going to end up version chasing every few months.
An alternative would be to use LTSC VMs (and install patches)
Other issues:
The AdoptOpenJDK does not yet currently support 2019ltsc or 1909 images. There is a PR to add them (https://github.com/AdoptOpenJDK/openjdk-docker/pull/365) but that has been sat for a while.
Gareth Evans
added a comment - Latest Update
Windows Docker images need to build on exactly the same kernel version as the host.
This means that, if we update the host, we need to update https://github.com/jenkinsci/docker/blob/master/8/windows/windowsservercore-1809/openj9/Dockerfile#L2 (and all other assorted builds) - this needs to be done at the same time that the new base images are deployed.
We could tag the VMs with `1909`/`1809` and support both builds for a period of time? But we’re going to end up version chasing every few months.
An alternative would be to use LTSC VMs (and install patches)
Other issues:
The AdoptOpenJDK does not yet currently support 2019ltsc or 1909 images. There is a PR to add them ( https://github.com/AdoptOpenJDK/openjdk-docker/pull/365 ) but that has been sat for a while. I think we want a Windows Server 2019 image so we can use docker. The whole point of a newer Windows image is to be able to build newer docker images.
az vm image list --offer Windows-10 --all --query "[].{publisher:publisher, sku:sku, version:version}" -o table
Lists all the skus for Windows 10.
Gareth Evans
added a comment - az vm image list --offer Windows-10 --all --query "[].{publisher:publisher, sku:sku, version:version}" -o table
Lists all the skus for Windows 10. I think https://github.com/jenkins-infra/packer-images/pull/35 gets us a 1909 image on azure.
Gareth Evans
added a comment - I think https://github.com/jenkins-infra/packer-images/pull/35 gets us a 1909 image on azure. I have a PR to upgrade the AWS packer image to the 2004 release instead of 1909. I haven't found a good version on Azure yet.
Since its EOL we can close the isssue