Run build for MUXControlsReleaseTest on WinDevPool-S instead of windows-2019 #5711
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
ghost
added
the
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ranjeshj
approved these changes
Aug 18, 2021
ranjeshj
pushed a commit
that referenced
this pull request
Aug 18, 2021
StephenLPeters
added
area-DevInternal
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.
We were using the 'windows-2019' pool to build MUXControlsReleaseTest.sln. This pool is the public pool that is provided by Azure Pipelines. It gets updated with new dependencies on a regular basis. However we are regularly running into issues where these updates cause out Pipelines to get broken.
So we switch over these Jobs to run on a pool using the same images that we use for running the main product build Job. I created WinDevPool-S and WinDevPoolOSS-S for this purpose. These are identical to WinDevPool-L and WinDevPoolOSS-L except they have lower machine specs (2 cores vs 8 cores).
This should make our build Pipelines more reliable.