-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Update Ubuntu 25.10 to 26.04 #121730
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
Update Ubuntu 25.10 to 26.04 #121730
Conversation
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 Ubuntu version references in Helix CI/CD pipeline configurations from 25.10 (October 2025, now GA) to 26.04 (April 2026, currently in preview). The changes prepare the build infrastructure for testing against the upcoming Ubuntu LTS release.
- Updated all Ubuntu version references from 25.10 to 26.04 across pipeline configuration files
- Modified both queue names and container image references to use the new version
- Updated comments to reflect the new "latest" Ubuntu version
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| eng/pipelines/libraries/helix-queues-setup.yml | Updated Ubuntu ARM64 and AMD64 queue configurations to use 26.04 containers |
| eng/pipelines/installer/helix-queues-setup.yml | Updated Ubuntu ARM64 queue configuration to use 26.04 container |
| eng/pipelines/helix-platforms.yml | Updated platform variable definitions and comments for Ubuntu x64 and ARM64 to reference 26.04 |
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
PR validation looks good. Now testing extra platforms. |
|
Extra platforms looks clear as well. I didn't see any failures for Ubuntu 26.04. I do see it present in passing build legs. This is the same dance we have played before. Are you OK taking in preview Ubuntu 26.04 into runtime main @jkotas? We did that with Debian 13 and Ubuntu 25.04 and 25.10 and it seemed to work out. Note that I deleted 25.10 and 25.04 images from the pre-reqs repo. I believe 25.10 is also in |
LGTM |
|
/ba-g "Known issues and problems with unrelated build/test legs" |
Fixes Issue <!-- N/A --> main PR #121730 # Description Backports Ubuntu container version updates from main. Changes Ubuntu 25.10 (preview during initial addition) to 26.04 (now in preview with official container releases) for Helix test infrastructure. Updates three container references: - `eng/pipelines/installer/helix-queues-setup.yml`: Linux ARM64 - `eng/pipelines/libraries/helix-queues-setup.yml`: Linux ARM64 and AMD64 All changes target container images only (`@mcr.microsoft.com/dotnet-buildtools/prereqs:ubuntu-26.04-*`). VM references remain unchanged. The `helix-platforms.yml` file does not exist in release/10.0. # Customer Impact No direct customer impact. Infrastructure change to align test environments with current Ubuntu preview release. # Regression No. This is a proactive infrastructure update. # Testing Changes are configuration-only. CI validation in main has been completed per the original PR. # Risk Low. Container references already validated in main branch. No code changes, only test infrastructure configuration. <!-- START COPILOT CODING AGENT SUFFIX --> <details> <summary>Original prompt</summary> > Please apply PR #121730 to the release/10.0 branch. I don't think the helix-platforms.yml file exists there. Please do not create it. > > #121730 > > The goal after this change is that all Ubuntu container references are using Ubuntu 26.04. Do not change VM references. Those will be handled separately. </details> <!-- START COPILOT CODING AGENT TIPS --> --- ✨ Let Copilot coding agent [set things up for you](https://github.com/dotnet/runtime/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo. --------- Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: richlander <[email protected]>
mainand then move to servicing when we're comfortable.