Skip to content

[9.0] Update CI OSes #115503

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: release/9.0-staging
Choose a base branch
from

Conversation

richlander
Copy link
Member

@richlander richlander commented May 13, 2025

@Copilot Copilot AI review requested due to automatic review settings May 13, 2025 00:37
Copy link
Contributor

@Copilot 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 updates the CI configuration to refresh the list of OS images used in the Helix queues setup, aligning with recent changes in supported OS versions.

  • Removed outdated or restructured OS images
  • Added new OS definitions (e.g., AzureLinux.3.0)
  • Reordered some image entries for clarity
Comments suppressed due to low confidence (2)

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

  • [nitpick] The new AzureLinux entry uses 'Ubuntu.2204.Amd64.open' with lowercase 'open' in the tag, which differs from other entries that use 'Open'. Consider standardizing the casing for consistency and clarity.
- (AzureLinux.3.0.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:azurelinux-3.0-helix-amd64

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

  • [nitpick] The re-introduction of the Centos.9 entry here may require verification against the previously removed entry. Confirm that this change is intentional and that it correctly reflects the supported Centos-stream version.
- (Centos.9.Amd64.Open)[email protected]/dotnet-buildtools/prereqs:centos-stream9-helix

@richlander
Copy link
Member Author

/azp run runtime-libraries-coreclr outerloop-linux

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@richlander
Copy link
Member Author

These issues all look existing.

@carlossanlop

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