Closed moerketh closed 2 years ago
so how to fix this ? what steps I need to follow to update vs2017-win2016 to latest one
@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.
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/ https://github.com/actions/virtual-environments/issues/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.