Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Pipelines "vs2017-win2016" vm image retires next month #1251

Closed
moerketh opened this issue Feb 10, 2022 · 2 comments · Fixed by #1261
Closed

Azure Pipelines "vs2017-win2016" vm image retires next month #1251

moerketh opened this issue Feb 10, 2022 · 2 comments · Fixed by #1261
Labels
Feature Feature Work required.

Comments

@moerketh
Copy link
Contributor

Looking at the pipelines in Azure DevOps I found that he current image in use in the Azure Pipelines "vs2017-win2016" is currently deprecated and retirement is planned for march 15 2022. The pipelines should be updated before that date. Brownouts are scheduled in the mean time. See also:
https://devblogs.microsoft.com/devops/hosted-pipelines-image-deprecation/
actions/runner-images#4312

The recommended change is to use "windows-latest" instead.

Here is a list where this image is currently in use:
azure-pipelines-pr.yml lines 84, 200, 224
azure-pipelines-merge.yml lines 44, 204, 228
azure-pipelines-create-release.yml lines 68
doc/samples.md line 266

I can send a PR for the replaces if needed.

@moerketh moerketh added the Feature Feature Work required. label Feb 10, 2022
@bharatbuddhadevphyrem
Copy link

bharatbuddhadevphyrem commented Mar 10, 2022

so how to fix this ? what steps I need to follow to update vs2017-win2016 to latest one

@moerketh
Copy link
Contributor Author

@bharatbuddhadevphyrem hi! Did you look at the attached PR for the suggested fix?
Basically replace 'vs2017-win2016' with 'windows-latest'. Looks like the pipelines are happy with that change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Feature Work required.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants