-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Update OpenSUSE container references to 16.0 #122373
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
base: release/10.0
Are you sure you want to change the base?
Conversation
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
Co-authored-by: richlander <[email protected]>
There was a problem hiding this 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 OpenSUSE container reference in Helix pipeline configuration from version 15.6 to 16.0 to align with current OpenSUSE releases. This is an infrastructure-only change for CI/CD testing pipelines.
Key changes:
- Updated Helix queue name and container image references from OpenSUSE 15.6 to 16.0
- Change applies to Linux x64 CoreCLR extra-platforms inner loop testing
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Fixes Issue
main PR
Description
Updates OpenSUSE container version from 15.6 to 16.0 in Helix pipeline configuration for Linux x64 CoreCLR extra-platforms testing.
Changed in
eng/pipelines/libraries/helix-queues-setup.yml:openSUSE.15.6.Amd64.Open→openSUSE.16.0.Amd64.Openopensuse-15.6-helix-amd64→opensuse-16.0-helix-amd64Customer Impact
None. Infrastructure-only change for CI/CD pipeline testing.
Regression
No. This is a container version update to align with current OpenSUSE releases.
Testing
YAML configuration change only. Will be validated through pipeline execution.
Risk
Low. Single line change updating container version reference. Helix infrastructure handles container availability. If container is unavailable, pipeline will fail gracefully without impacting releases.
Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.