Update the agent pool for the PR builds #19102
Merged
+16
−38
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
Contributor
|
abonie
added
the
NO_RELEASE_NOTES
Member
Author
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
abonie
commented
Nov 19, 2025
abonie
commented
Nov 19, 2025
Member
Author
|
Seems like the newer agent queue is not available for NetCore-Public pool |
T-Gro
reviewed
Nov 20, 2025
T-Gro
approved these changes
Nov 20, 2025
This was referenced Nov 21, 2025
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.
The scouting pipeline mentioned in the comments hasn't been updated in many years and so it doesn't seem to provide much value. We should get rid of it. Let's stop relying on pipeline variable for the agent pool and update it to vs2026 queue.