Hello 
We are deprecating the following Windows images on CircleCI and will be removing them from our platform on Sept 30, 2024:
Tags:
- windows-server-2019:201908-06
- windows-server-2019:201908-08
- windows-server-2019-vs2019:201908-02
- windows-server-2019-vs2019:201908-06
- windows-server-2019-vs2019:201909-25
- windows-server-2019-vs2019:201911-06
- windows-server-2022-gui:2022.04.1
- windows-server-2022-gui:2022.07.1
- windows-server-2022-gui:2022.08.1
- windows-server-2022-gui:2022.09.1
- windows-server-2022-gui:2023.03.1
- windows-server-2022-gui:2023.04.1
- windows-server-2022-gui:2023.06.1
- windows-server-2022-gui:2023.07.1
- windows-server-2022-gui:2023.09.1
- windows-server-2022-gui:2023.11.1
- windows-server-2019-nvidia:201908-28
- windows-server-2019-nvidia:201909-25
- windows-server-2019-nvidia:201911-06
Once an image is removed, the CircleCI jobs that use that image will fail with an error message - This job was rejected because the image is unavailable .
CircleCI will email impacted users with a list of projects that must be updated before the EOL date.
Why are these images being deprecated?
To ensure pipelines on CircleCI run with the highest level of reliability & security.
What do I need to do?
You will need to update your CircleCI config to use a valid Windows image as per the tagging conventions in our Windows Image Policy.
The recommended tags to use are as follows:
default- latest stable version and version if do not specify anythingprevious- Previousdefaultversionedge- Development image of latest image
A couple examples:
Before:
resource_class: 'windows.medium'
machine:
image: windows-server-2019:201908-06 // any of the deprecated image tags above
After:
resource_class: 'windows.medium'
machine:
image: default
resource_class: 'windows.medium'
machine:
image: windows-server-2022-gui:previous
resource_class: 'windows.medium'
machine:
image: windows-server-2022-gui:edge
Updating the CircleCI Windows Orb
You may need to make additional changes to your config if you are using an Orb that selects a machine image for you. If you’re using an old and outdated version of the CircleCI Windows Orb that uses a deprecated image by default you’ll need to either:
- Upgrade the
circleci/windowOrb to a more recent version (the most recent version of the Orb uses a non-deprecated image by default). This is the recommended course of action. - Ensure that you are explicitly passing in, via the
versionparameter to thedefaultexecutor, a non deprecated image version to use (e.g.current).
What will happen after the Sept 30 EOL Date?
If you do not currently specify an image, your job will keep the same behavior, and use the default tag automatically.
Calling any of the deprecated image tag versions directly will cause your job to fail.
Brownout Schedule and EOL
We will be conducting brownouts for the above images on the following dates and times.
- 29 January 2024
- 07:00 UTC → 11:00 UTC
- 13:00 UTC → 17:00 UTC
- 20:00 UTC → 00:00 UTC
- 30 April 2024
- 01:00 UTC → 11:00 UTC
- 13:00 UTC → 23:00 UTC
- 31 July 2024
- 00:00 UTC → 00:00 UTC (24 Hour)
- 18 September 2024
- 00:00 UTC → 00:00 UTC (24 Hour)
- 30 September 2024
- Deprecated tags are removed and will be unavailable
During these times, all jobs calling these images will fail. Please update your configs as soon as possible to prevent any disruption to your pipelines.
The default tag is available for you to transition to as of writing and we highly recommend updating your config to avoid job failure during these brownouts. If you have already updated your tags, please disregard this email.
What’s Next?
Details on how we manage and maintain our Linux images can be found here: Windows Image Policy.
Feedback
If you have any questions, comments, or concerns, please post a reply in this thread and we will be happy to help!
Respectfully,
CircleCI Images Team