[release/5.0] Use NetCorePublic-Pool pool instead of AzDO hosted pool for Browser jobs #43598
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
… for Browser jobs (dotnet#43589) The hosted pool runs into no disk space issues.
|
Tagging subscribers to this area: @safern, @ViktorHofer |
safern
approved these changes
Oct 19, 2020
This was referenced Oct 19, 2020
|
This falls under infrastructure work necessary to ship/service. Fine to merge |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The hosted pool runs into disk space issues. Looks like AzDO provides less free space recently and we're hitting no free space when building Browser wasm tests.
Backport of #43589 to release/5.0
Customer Impact
None, this impacts our CI only and allows us to build.
Testing
Tested on the #43589 PR.
Risk
Low, it just changes the build pool we're using for running the Browser wasm build (which runs in a Docker container anyway).