Skip to content

Switch publish jobs to -Svc pools for release/9.0#16750

Closed
missymessa wants to merge 2 commits intorelease/9.0from
missymessa/svc-pool-9.0
Closed

Switch publish jobs to -Svc pools for release/9.0#16750
missymessa wants to merge 2 commits intorelease/9.0from
missymessa/svc-pool-9.0

Conversation

@missymessa
Copy link
Copy Markdown
Member

Replace hardcoded NetCore1ESPool-Publishing-Internal with the DncEngInternalBuildPool variable so publish/post-build jobs use -Svc pools on release branches via pool-providers.yml dynamic resolution.

Changes

  • publish-build-assets.yml: NetCore1ESPool-Publishing-Internal → ``
  • post-build.yml: NetCore1ESPool-Publishing-Internal → ``

Context

The Publish Assets stage was hardcoded to use NetCore1ESPool-Publishing-Internal regardless of branch. Since pool-providers.yml is already imported in these templates, using the variable ensures release branch builds run on -Svc pools as intended.

missymessa and others added 2 commits April 23, 2026 15:47
Servicing branches should use -Svc pools for proper billing separation
(COGS) and queue isolation. The dynamic pool-providers.yml expression
was not correctly routing these builds to the -Svc pool.

Hardcode -Svc pool names directly since this branch will always be a
servicing branch.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Replace hardcoded NetCore1ESPool-Publishing-Internal with the
DncEngInternalBuildPool variable so publish jobs use -Svc pools
on release branches via pool-providers.yml dynamic resolution.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

1 participant