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 <panbingkun@baidu.com> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
|
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 🙇 .
|
|
@voxpelli it would be easier to test and have a canary workflow if there were a sliding -beta tag, I use -latest but it is difficult as maintainer in a bunch of repos to go around manually changing them all to a numbered release tag that will then be obsolete after |
|
Additionally, there's an existing deprecation message vehicle for actions that could be used - the warnings that pop up when you're indirectly using an about-to-be-removed node runtime, for example. |
That would be great! Create an issue if there is none! Maybe -next would be even better? Or both?
Those changes are breaking changes within an existing runner image I believe, not about moving to a new image |
|
If |
Providing different packages or not providing others is not about stability. |
|
If smaller image would mean that my workflows start much faster, I would be fine installing the deps myself, especially if installation is shorter than time saved on starting the job. Unfortunately I have not observed this… What I liked in gitlab CI was that it allowed you to use any docker image. Which would mean anybody could prepare an image shaved to his needs. But I guess than you would run the trouble of caching those images on the runners…? |
|
For one of our workflows, it was the rollback to |
|
I though it was GitHub bugs that rolling |
|
If the action/workflow is set to a value that doesn't exist, will it fail? Or just wait? I changed |
|
@jr0me it should be |
|
the agent names are documented here for github actions: https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories and here for Azure Pipelines: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software Although it doesn't answer the question of what the expected behaviour is when specifying an agent pool that doesn't exist. |
I have no idea what's going on with the transition from ubuntu-latest from 22.04 to 24.04. It switched to 24.04, and now it looks like it's back to 22.04... See actions/runner-images#10636
I have no idea what's going on with the transition from ubuntu-latest from 22.04 to 24.04. It switched to 24.04, and now it looks like it's back to 22.04... See actions/runner-images#10636
This pins the generate-docs GH workflow to run on a fixed version of ubuntu so we get defined semantics of `pip install` wrt system packages. We were previously using the `ubuntu-latest` image and GH has been switching this from ubuntu-22.04 to 24.04 and back again, also see actions/runner-images#10636.
This pins the generate-docs GH workflow to run on a fixed version of ubuntu so we get defined semantics of pip install wrt system packages. We were previously using the ubuntu-latest image and GH has been switching this from ubuntu-22.04 to 24.04 and back again, also see actions/runner-images#10636.
and others
NOTICE: THIS ROLLOT HAS BEEN PUT ON HOLD
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 in September 25th, 2024. We plan to complete the migration by October 30th , 2024.
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.
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.04We support two latest LTS Ubuntu versions, so Ubuntu 22 will still be available in near future.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: