Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Azure deprecating windows-2016 environment
See original GitHub issueSeeing this warning on CI:
##[warning]The windows-2016 environment will be deprecated on November 15, 2021, and removed on March 15, 2022. Migrate to windows-latest instead. For more details see https://github.com/actions/virtual-environments/issues/4312
Issue Analytics
- State:
- Created 2 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
Azure DevOps: Migrating to windows-latest - Novacare Blog
Microsoft is deprecating and removing the windows-2016 environments in DevOps in the coming months. Here's how to change the agent ...
Read more >Error Deploying Release Pipeline Windows 2016 deprecated
The release pipeline agent needs changing from 2016 to 2019 or whatever you build on as long as its > 2016.
Read more >I am getting error during build pipeline on azure devops
Your open channel to Microsoft engineering teams. Select a page ... The windows-2016 environment is deprecated and will be removed on...
Read more >Hosted Pipelines Image Deprecation - Azure DevOps Blog
In this blog post we want to update you on recent and upcoming changes for Microsoft-hosted macOS, Windows & Ubuntu images.
Read more >Azure DevOps Error - This is a scheduled windows - Konabos
Steps on how to resolve the error - This is a scheduled windows-2016 brownout. The windows-2016 environment is deprecated and will be ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
There’s no trade-off. We just need to make sure that the conda compiler activation script works. The effort needed is probably less than the time we have spent on writing on this issue.
We’ll need to see if vc141 toolchain works there.