Switch to 1ES servicing pools on release/6.0 #5372
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
jonfortescue
requested review from
MattGal,
lpatalas,
ulisesh and
vatsan-madhavan
ghost
requested review from
MattGal
approved these changes
Sep 22, 2021
Member
MattGal
left a comment
MattGal
left a comment
There was a problem hiding this comment.
I don't think the casing matters, but if it does somehow you've left it off line 38 of eng/pipeline.yml
Contributor
Author
|
@MattGal just trying to match the original files -- it doesn't matter, purely a style thing. :) |
This was referenced Sep 30, 2021
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.
2 participants
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.
Tracking Issue: https://github.com/dotnet/core-eng/issues/14276
Main PRN/ADescription
We need to move over to 1ES servicing pools for servicing branches. This accomplishes this in release/6.0.
Customer Impact
N/A
Regression
None.
Testing
N/A
Risk
If tests fail in this PR, it's due to interactive mode not being turned on. That's being tracked here: https://github.com/dotnet/core-eng/issues/14358.