Skip to content

Avoid broken NetCore1ESPool-Svc-Internal pool#81023

Merged
jjonescz merged 1 commit intodotnet:mainfrom
jjonescz:svc-machines
Nov 4, 2025
Merged

Avoid broken NetCore1ESPool-Svc-Internal pool#81023
jjonescz merged 1 commit intodotnet:mainfrom
jjonescz:svc-machines

Conversation

@jjonescz
Copy link
Member

@jjonescz jjonescz commented Nov 4, 2025

Fixes (or works around?) broken official builds. Validation: https://dev.azure.com/dnceng/internal/_build/results?buildId=2831147&view=results

@jjonescz jjonescz marked this pull request as ready for review November 4, 2025 17:11
@jjonescz jjonescz requested a review from a team as a code owner November 4, 2025 17:11
@jjonescz jjonescz merged commit e179ab4 into dotnet:main Nov 4, 2025
5 of 6 checks passed
@jjonescz jjonescz deleted the svc-machines branch November 4, 2025 18:05
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Nov 4, 2025
@JoeRobich
Copy link
Member

@jjonescz Does this need backported to servicing branches?

@jjonescz
Copy link
Member Author

jjonescz commented Nov 4, 2025

I assume the Svc pool will be fixed, and that this is just a temporary issue. Also I'm told that we should use eng/common/templates/variables/pool-providers.yml instead of hard-coding the pool names, so I will probably follow up with that change.

@jjonescz
Copy link
Member Author

jjonescz commented Nov 4, 2025

Also I'm told that we should use eng/common/templates/variables/pool-providers.yml instead of hard-coding the pool names, so I will probably follow up with that change.

Which would actually use Svc pools for servicing branches... :D

@jjonescz
Copy link
Member Author

jjonescz commented Nov 5, 2025

/backport to release/dev18.3

@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2025

Started backporting to release/dev18.3 (link to workflow run)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants