Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[release/5.0] Use NetCorePublic-Pool pool instead of AzDO hosted pool for Browser jobs #43598

Merged
merged 1 commit into from
Oct 20, 2020
Merged

[release/5.0] Use NetCorePublic-Pool pool instead of AzDO hosted pool for Browser jobs #43598

merged 1 commit into from
Oct 20, 2020

Conversation

akoeplinger
Copy link
Member

@akoeplinger akoeplinger commented Oct 19, 2020 •
edited
Loading

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).

@akoeplinger
[release/5.0] Use NetCorePublic-Pool pool instead of AzDO hosted pool…
d0211b0 
… for Browser jobs (dotnet#43589)

The hosted pool runs into no disk space issues.
@ghost
Copy link

ghost commented Oct 19, 2020

Tagging subscribers to this area: @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

@akoeplinger akoeplinger mentioned this pull request Oct 19, 2020
Merged
This was referenced Oct 19, 2020
Closed
Open
Closed
Closed
Closed
Closed
@lewing lewing mentioned this pull request Oct 19, 2020
Merged
@runfoapp runfoapp bot mentioned this pull request Oct 20, 2020
Closed
@lewing lewing added the arch-wasm WebAssembly architecture label Oct 20, 2020
@lewing lewing mentioned this pull request Oct 20, 2020
Merged
@lewing lewing added the Servicing-consider Issue for next servicing release review label Oct 20, 2020
@safern
Copy link
Member

safern commented Oct 20, 2020

@danmosemsft @mmitche @Anipik this is infra only change, can we merge?

@lewing lewing mentioned this pull request Oct 20, 2020
Merged
@danmoseley
Copy link
Member

This falls under infrastructure work necessary to ship/service. Fine to merge

@lewing lewing merged commit 2ccdaf8 into dotnet:release/5.0 Oct 20, 2020
@lewing lewing removed the Servicing-consider Issue for next servicing release review label Oct 20, 2020
@akoeplinger akoeplinger deleted the use-netcorepublic-5.0 branch October 20, 2020 10:22
@mmitche mmitche added this to the 5.0.1 milestone Nov 3, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@safern safern safern approved these changes

@danmoseley danmoseley Awaiting requested review from danmoseley

@mmitche mmitche Awaiting requested review from mmitche

@Anipik Anipik Awaiting requested review from Anipik

Assignees
No one assigned
Labels
arch-wasm WebAssembly architecture area-Infrastructure-libraries
Projects
None yet
Milestone
5.0.1
Development

Successfully merging this pull request may close these issues.
5 participants
@akoeplinger @safern @danmoseley @lewing @mmitche