Skip to content

[release/11.0] Fix internal Helix pipeline credentials and queue selection - #133938

Merged
akoeplinger merged 1 commit into
dotnet:release/11.0from
akoeplinger:backport/release-11.0-helix-pipeline-fixes
Sep 21, 2026
Merged

akoeplinger merged 1 commit into
dotnet:release/11.0from
akoeplinger:backport/release-11.0-helix-pipeline-fixes

Conversation

@akoeplinger

Copy link
Copy Markdown
Member

Summary

Backports three Helix pipeline fixes to release/11.0:

Backport adaptations

Preserves release's Windows queue literals and all container image digests. The Windows-alias hunk from #133704 is omitted because release does not have the rolling-Windows migration. No queue-version upgrades or new test lanes are included.

Validation

  • Parsed all seven modified YAML files.
  • Checked public/internal queue mappings, alias resolution, and monitor credential guards.
  • Confirmed unrelated YAML data and all container digests are unchanged.
  • git diff --check passed.

No product build or Azure DevOps pipeline run was performed; these changes are pipeline YAML only. CI must validate Azure DevOps template expansion and execution.

Note

This backport and PR description were prepared with GitHub Copilot.

…ction

Backport dotnet#133885, dotnet#133704, and dotnet#133878. Preserve release Windows queue literals and container image digests; omit the main-only Windows alias migration hunk.

Upstream commits:
8d1cc30
bd6d336
cbe94bf

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

@akoeplinger akoeplinger added the Servicing-approved Approved for servicing release label Sep 15, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

Azure DevOps template expansion and execution were not validated by a pipeline run.

Pull request overview

Backports Helix pipeline credential and queue-selection fixes to release/11.0.

Changes:

  • Enables monitor credentials for internal PR runs.
  • Selects internal macOS/Apple queues explicitly.
  • Updates WASI tests to use CoreCLR queue mappings.
File summaries
File Description
eng/pipelines/runtime.yml Internal monitor credentials
eng/pipelines/performance/perf.yml Internal performance credentials
eng/pipelines/libraries/helix-queues-setup.yml Library queue aliases
eng/pipelines/installer/helix-queues-setup.yml Installer queue aliases
eng/pipelines/coreclr/templates/helix-queues-setup.yml WASI queue mapping
eng/pipelines/common/templates/wasi-wasm-coreclr-runtime-tests.yml CoreCLR queue setup
eng/pipelines/common/templates/wasi-wasm-coreclr-build-only.yml Queue mapping reference
Review details
  • Files reviewed: 7/7 changed files
  • Comments generated: 0
  • Review effort level: Lite

@akoeplinger

Copy link
Copy Markdown
Member Author

/ba-g unrelated test failures

@ViveliDuCh

Copy link
Copy Markdown
Member

Hi,

the code complete date for RC2 is Monday 21st September. Make sure to merge this PR on that date at the latest, or it won't make it into that release.

As a reminder, if this is a product change, you also need Tactics approval before merging this PR (test-only or infra-only changes don't require Tactics approval).

@akoeplinger
akoeplinger merged commit fa239c2 into dotnet:release/11.0 Sep 21, 2026
159 of 162 checks passed
@dotnet-milestone-bot dotnet-milestone-bot Bot added this to the 11.0-rc2 milestone Sep 21, 2026
@akoeplinger
akoeplinger deleted the backport/release-11.0-helix-pipeline-fixes branch September 24, 2026 10:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-Infrastructure Servicing-approved Approved for servicing release

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants