Add pool provider template reference #82452
Merged
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
MattGal
approved these changes
Feb 21, 2023
MattGal
approved these changes
Feb 21, 2023
jkoritzinsky
approved these changes
Feb 21, 2023
|
@jkoritzinsky I tried, the yml fails to expand sadly. something already defines a variable scope globally. |
hoyosjs
added
the
NO-MERGE
|
Dang. Let's just go with this then. |
There are some... compromises... in the eng/common folder's usage of the same for the same reason. I'm just happy it can work at all. |
|
verifies the internal build used the variables were properly expanded. |
|
/azp run runtime-libraries enterprise-linux |
|
Azure Pipelines successfully started running 1 pipeline(s). |
hoyosjs
removed
the
NO-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.
Use template to determine pool provider to use.
The provider can't be expanded in the pipeline-with-resources step as the expansion breaks once global variables are consolidated. All variables end up in the global scope correctly, but several expansion points are expanded before assignment - particularly the ones at the pipeline scope - meaning that several parameters derived from them are empty and cause issues in further expansion decisions.