Update build and test images to Alpine 3.22

[richlander]

• Updated build and test images to Alpine 3.22.
• Commented out the reference to Alpine Edge. We should only be using/running that in main. Will bring that back after the RC snap and when preparing for Alpine 3.23 becomes relevant.
• A hypothesis was that Alpine Edge would not be too noisy and that we'd be clean on Alpine 3.vNext from the get-go. Let's see!

Related:

• https://alpinelinux.org/posts/Alpine-3.22.0-released.html
• Add Alpine 3.22 images dotnet-buildtools-prereqs-docker#1442
• Add images for Alpine 3.22 dotnet-docker#6464

[Copilot]

Pull Request Overview

This PR updates the build and test images to Alpine 3.22 while commenting out the Alpine Edge builds for non‑main branches. Key changes include:

• Updating image tags from alpine-3.21 to alpine-3.22 in various pipeline YAML files.
• Commenting out the Alpine Edge build references to restrict their use to the main branch.
• Ensuring consistency across library, installer, coreclr templates, and common pipeline resource configurations.

Reviewed Changes

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

File	Description
eng/pipelines/libraries/helix-queues-setup.yml	Updated Alpine image version and commented out Alpine Edge.
eng/pipelines/installer/helix-queues-setup.yml	Updated the Alpine image version for the installer pipeline.
eng/pipelines/coreclr/templates/helix-queues-setup.yml	Updated image tags for both public and internal pipelines.
eng/pipelines/common/templates/pipeline-with-resources.yml	Updated Alpine image version in common pipeline resources.

Comments suppressed due to low confidence (5)

eng/pipelines/libraries/helix-queues-setup.yml:40

• Confirm that the Alpine Edge build references remain commented out for non‑main branches as intended.

# Alpine edge builds should only be used in main

eng/pipelines/libraries/helix-queues-setup.yml:44

• Verify that the updated Alpine 3.22 image tag is supported by all dependent build tools and environments.

- (Alpine.322.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:alpine-3.22-helix-amd64

eng/pipelines/installer/helix-queues-setup.yml:36

• Ensure that the update to Alpine 3.22 in the installer pipeline is validated within the AzureLinux environment.

- (Alpine.322.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:alpine-3.22-helix-amd64

eng/pipelines/coreclr/templates/helix-queues-setup.yml:80

• Confirm that both public and internal pipeline configurations intentionally use the Alpine 3.22 image tag.

- (Alpine.322.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:alpine-3.22-helix-amd64

eng/pipelines/common/templates/pipeline-with-resources.yml:70

• Check that the update to Alpine 3.22 in the common pipeline resource template is compatible with the overall pipeline configuration.

image: mcr.microsoft.com/dotnet-buildtools/prereqs:alpine-3.22-amd64

[dotnet-policy-service]

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

[richlander]

Looks like this change came out clean. Just need an approval now.

[jkotas]

/azp run runtime-libraries-coreclr outerloop-linux

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[richlander]

Good call. Running outer loop occurred to me. Will do that next time.

BA is now green.

[jkotas]

I do not see the alpine edge running in outer loop, so this condition is probably not right.

@jkoritzinsky Do you happen to know how to check for main vs. servicing here?

[richlander]

Good call on checking. I did not do that.

[richlander]

I was thinking about doing the same thing for Fedora, just testing it in main. It would be nice to just have one fast-moving distro in servicing to maintain. We get significant RHEL-family coverage from CentOS Stream and Alma Linux. I think that + Fedora in main is a good model.