Update Viper machines to use windows-2025 vm image #4885
Merged
Conversation
This file contains hidden or 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
… rather than the depreciating windows 2019. This matches what the other windows machines have been using, the viper PR and windows update pr just missed each other slightly.
LoopedBard3
added
lab-infrastructure
dependencies
caaavik-msft
approved these changes
Jul 11, 2025
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.
Update viper machines to use windows-2025 vm image for pre-test steps rather than the depreciating windows 2019. This matches what the other windows machines have been using, the viper PR and windows update pr just missed each other slightly.
Internal test run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2747539&view=results