-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Ubuntu-latest workflows will use Ubuntu-24.04 image #10636
Comments
The more I look at this list the more I realize that 24.04 is a step back for a lot of people. People are going to complain when this becomes the ubuntu-latest. Be aware of this and maybe make sure this communication is shown on github/azure devops But thanks for the heads up! |
ubuntu-24.04 is still labeled Will you now be removing the |
Yes @MikeMcC399 . Its updated and removed. |
@ThibaultLesuisse are you aware that NuGet refers specifically to NuGet.exe (which requires mono on Mac & Linux), as does Azure Pipeline's If you're building your projects with |
But we need NuGet.exe to sync our custom Artifacts store. And yes I know that commonly you need to run mono nuget.exe to run it on Mac/Linux. But it doesn't change the fact that a lot of tools are now missing for various reasons. This should be communicated. |
We're also affected by the removal of Mono. The official Mono repo only lists 20.04, but the package seem to work fine in newer versions–which is how the 22.04 image got Mono: runner-images/images/ubuntu/scripts/build/install-mono.sh Lines 15 to 18 in ae99c16
Is there a reason this can't be done for 24.04 as well? I tested it briefly and it's working for our relatively simple needs. Mono is fairly chunky so we'd rather not install it every single workflow run. |
…o `ubuntu-latest` ### What changes were proposed in this pull request? The pr aims to align the running OS image of `maven_test.yml` to `ubuntu-latest` (from `ubuntu-22.04` to `ubuntu-24.04`) ### Why are the changes needed? https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20240922.1 <img width="627" alt="image" src="https://github.com/user-attachments/assets/f42fd7ed-c52a-4b39-9a92-02657c53d734"> After actions/runner-images#10636, `ubuntu-latest` has already pointed to `ubuntu-24.04` instead of `ubuntu-22.04`. <img width="811" alt="image" src="https://github.com/user-attachments/assets/adf6b3a8-5ca5-4daa-b35d-ea1386fa07a6"> I have checked all tasks running on `Ubuntu OS` (except for the 2 related to `TPCDS`), and they are all using `ubuntu-latest`. Currently, only `maven_test.yml` is using `ubuntu-22.04`. Let's align it. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #48263 from panbingkun/SPARK-49797. Authored-by: panbingkun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
Hi there - my team is scrambling this morning due to this change. I have detailed the issue on the community forum here, but the tl;dr is that this version bump prevents Python packages from being installed for system Python. Unfortunately, it seems the evaluation of this issue was incorrect:
In fact, my team has a large number of workflows created by many different engineers, and around a dozen of our workflows that didn't previously leverage actions/setup-python now have to go through our internal change management process in order to restore stability to our CI/CD In the future, please announce breaking changes as a deprecation notice on the GitHub Blog. It's the one place we rely on to proactively catch and prevent stability issues from occurring in our pipelines |
This morning, several of our CI pipelines broke due to these changes. It would be great to have compatibility with the following dependencies, allowing us to upgrade the ubuntu version in the future without complicating our pipelines 🙇 .
|
This reverts commit 5ac342c. It seems they haven't switched to 24.04 yet: actions/runner-images#10636 Leave it as-is for now and we can revisit this if needed. Signed-off-by: Nick Kossifidis <[email protected]>
List of node versions need an update? Node 16 was already removed for ubuntu-24.04 in #10677 , right? |
There's an issue with the .NET SDK on the new Ub24 images - it's using a much older build of the SDK that has security vulnerabilities. Ubuntu 22 has .NET 8.0.403 installed, while Ubuntu 24 has .NET 8.0.110. Besides security vulnerabilities, this is causing issues in our build pipeline Can we have this updated to .NET 8.0.404 (which is the latest build), as well as have .NET 9 installed as well? |
@artiomchi is right, this is also a blocker in my opinion to move |
GitHub made ubuntu-24.04 generally available back in September via https://github.blog/changelog/2024-09-25-actions-new-images-and-ubuntu-latest-changes/ and is rolling it out to ubuntu-latest from December 5th as announced in actions/runner-images#10636. We are in no particular rush to update, but there's also no reason to stay behind given that our needs from the OS are rather basic. Moreover, since we pin the version, it can be easy to forget to update once ubuntu-latest does switch to 24.04 for everyone else. Signed-off-by: Daniel Martí <[email protected]> Change-Id: I3fe0823abb3bdea57078643b3e81725bd6e83b9f Dispatch-Trailer: {"type":"trybot","CL":1204343,"patchset":1,"ref":"refs/changes/43/1204343/1","targetBranch":"master"}
GitHub made ubuntu-24.04 generally available back in September via https://github.blog/changelog/2024-09-25-actions-new-images-and-ubuntu-latest-changes/ and is rolling it out to ubuntu-latest from December 5th as announced in actions/runner-images#10636. We are in no particular rush to update, but there's also no reason to stay behind given that our needs from the OS are rather basic. Moreover, since we pin the version, it can be easy to forget to update once ubuntu-latest does switch to 24.04 for everyone else. Signed-off-by: Daniel Martí <[email protected]> Change-Id: I3fe0823abb3bdea57078643b3e81725bd6e83b9f Reviewed-on: https://review.gerrithub.io/c/cue-lang/cue/+/1204343 TryBot-Result: CUEcueckoo <[email protected]> Unity-Result: CUE porcuepine <[email protected]> Reviewed-by: Paul Jolly <[email protected]>
- The Ubuntu build and install fails possibly due to this: actions/runner-images#10636 - On MacOS `brew` fails to install pkgconfig: apache/arrow#44820
I'm a bit confused about the choices made for Node.JS here, considering that both Ubuntu and Node bumps once a year, and that node 16 security support is long gone now, and 22 is the officially recommended LTS. Current plan: Ubuntu 22: 16.* (cached) Ubuntu 24: 16.* (cached) Suggested change: To have 22 as default given that both node 18/20 security support will end in 5 mo and 1y 5mo respectively, which presumably is before you'll replace this image with Ubuntu 26 in two years time: Ubuntu 24: 18.* (cached) |
For Leiningen users — consider setup-clojure action. - name: Install clojure tools
uses: DeLaGuardo/[email protected]
with:
lein: latest |
@artiomchi @mario-d-s if you have a look at the docs for installing the .NET SDK on Ubunutu 24.04, the table shows that Microsoft is no longer providing any builds for Ubuntu 24.04. This means only Ubunutu's own build of the .NET SDK is available. For reasons I don't understand, Ubunutu, Redhat, and any other Linux distro that uses the https://github.com/dotnet/dotnet mono-repo only get the .1xx SDKs, never the 200, 300, or 400 builds that Microsoft builds. Additionally, if you look at the .NET 8 releases page, https://dotnet.microsoft.com/en-us/download/dotnet/8.0, the 8.0.11 runtime came out with 3 SDKS in November, 8.0.404, 8.0.307 and 8.0.111. In October, the 8.0.10 runtime came out with the 8.0.403, 8.0.306, and 8.0.110 SDKs. So, the 8.0.110 SDK was current and fully patched as of October's Patch Tuesday, although there is an update since the November Patch Tuesday. But it's only 1 build old, not a "much older build". |
On December 5th, the `ubuntu-latest` runner will start pointing to Ubuntu 24: actions/runner-images#10636 This updates all workflows to use Ubuntu 24 so we don't have any unexpected surprises. Signed-off-by: Mason Malone <[email protected]>
Rollout will begin on December 5th and will complete on January 17th, 2025.
Breaking changes
Ubuntu 24.04 is ready to be the default version for the "ubuntu-latest" label in GitHub Actions and Azure DevOps.
Target date
This change will be rolled out over a period of several weeks beginning December 5th and will complete on January 17th, 2025.
The motivation for the changes
GitHub Actions and Azure DevOps have supported Ubuntu 24.04 in preview mode since May 2024, and starting from July 2024 Ubuntu 24.04 is generally available for all customers. We have monitored customer feedback to improve the Ubuntu 24.04 image stability and now we are ready to set it as the latest. There are a set of packages listed below that we have removed from the Ubuntu 24 image. Please review the list carefully to see if you will be impacted by these changes. We have made cuts to the list of packages so that we can maintain our SLA for free disk space. The images have grown so large we are in danger of violating our SLA if we keep the package list as-is.
The factors we took into consideration when removing packages are as follows:
We understand that our reasoning may not make sense to some of you out there, but please bear in mind that we tried to keep disruptions as minimal as possible, and tried to keep the best interests of the community at large in mind. There is a very large and diverse community using our images, and as much as we would like to, we cannot pre-install every tool on these images.
Platforms affected
Mitigation ways
Steps or options for impact mitigation
If you see any issues with your workflows during transition period:
runs-on: ubuntu-22.04
We support two latest LTS Ubuntu versions, so Ubuntu 22 will still be maintained for the next 2 years.Software Differences
The Ubuntu 22.04 image has a different set of software than Ubuntu 24.04. The most significant changes are listed in the table below:
The text was updated successfully, but these errors were encountered: