Skip to content

[testing] Use LLVM 22#124937

Draft
sbomer wants to merge 1 commit intodotnet:mainfrom
sbomer:llvm-22
Draft

[testing] Use LLVM 22#124937
sbomer wants to merge 1 commit intodotnet:mainfrom
sbomer:llvm-22

Conversation

@sbomer
Copy link
Member

@sbomer sbomer commented Feb 27, 2026

Copilot AI review requested due to automatic review settings February 27, 2026 02:01
@sbomer sbomer added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Feb 27, 2026
@dotnet-policy-service
Copy link
Contributor

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

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR replaces container image references from the public Microsoft Container Registry (mcr.microsoft.com) to a private Azure Container Registry (svbomeracr.azurecr.io) for testing LLVM 22 toolchain changes in prerequisite Docker images (related to dotnet/dotnet-buildtools-prereqs-docker#1591). The PR title clearly indicates this is a "[testing]" change.

Changes:

  • All azurelinux-3.0-net11.0-* container images now reference the private svbomeracr.azurecr.io registry
  • Other container images (Ubuntu, Alpine, CentOS, Debian, etc.) continue to use the public MCR

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
eng/pipelines/common/templates/pipeline-with-resources.yml Updated 18 container image references for azurelinux-3.0-net11.0 variants to point to the private test registry
.github/workflows/jit-format.yml Updated container reference for the JIT format workflow to use the private test registry

containers:
linux_arm:
image: mcr.microsoft.com/dotnet-buildtools/prereqs:azurelinux-3.0-net11.0-cross-arm
image: svbomeracr.azurecr.io/dotnet-buildtools/prereqs:azurelinux-3.0-net11.0-cross-arm
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

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

This PR changes container image references from the public Microsoft Container Registry (mcr.microsoft.com) to a private Azure Container Registry (svbomeracr.azurecr.io) for testing purposes. This change should not be merged to the main branch as-is, as it would break builds for external contributors and the general public who do not have access to the private registry. Once testing is complete, these references should be reverted back to the public MCR, or the tested images should be published to MCR before merging.

Copilot uses AI. Check for mistakes.
- name: linux
image: ubuntu-latest
container: mcr.microsoft.com/dotnet-buildtools/prereqs:azurelinux-3.0-net11.0-cross-amd64
container: svbomeracr.azurecr.io/dotnet-buildtools/prereqs:azurelinux-3.0-net11.0-cross-amd64
Copy link

Copilot AI Feb 27, 2026

Choose a reason for hiding this comment

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

The private container registry (svbomeracr.azurecr.io) reference should not be merged to the main branch. External contributors and public builds will not have access to this private registry, which would cause build failures. After testing is complete, revert to the public MCR reference.

Suggested change
container: svbomeracr.azurecr.io/dotnet-buildtools/prereqs:azurelinux-3.0-net11.0-cross-amd64
container: mcr.microsoft.com/dotnet-buildtools/prereqs:azurelinux-3.0-net11.0-cross-amd64

Copilot uses AI. Check for mistakes.
@am11
Copy link
Member

am11 commented Feb 27, 2026

BA is green, all build issues are known. Opened dotnet/dotnet-buildtools-prereqs-docker#1597.

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

Labels

area-Infrastructure NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons)

Projects

Status: No status
Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants