Use windows-2019 instead of windows-lastest (temporarily) #1820
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
GitHub updated its GH Actions environments and
windows-latestis now 2022 by default (previously 2019). It caused our pipeline to fail.This commit brings back a
windows-2019environment in our GH Actions pipeline.Anything else we should know?
We will discuss the upgrade back to
windows-latestin #1819Briefly, I would like to use vswhere.exe in our pipeline to avoid hardcoding paths to Visual Studio.
Did you check all the boxes?
closes #XXXXin comment to auto-close issue when PR is merged)