Skip to content
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

Switch github workflows to ubuntu 22.04 #4607

Merged
merged 2 commits into from
Feb 12, 2025
Merged

Conversation

bcl
Copy link
Contributor

@bcl bcl commented Feb 11, 2025

Changes the github workflows to use ubuntu-22.04 everywhere.

bcl added 2 commits February 11, 2025 10:24
github is dropping support for 20.04 on 4/1/2025 so move to the next
stable version.

Also, back in commit e8ae7e7 we removed
use of ubuntu-latest because it can change unexpectedly. Some other uses
crept back in, so this changes those to use 22.04 as well.
We want to use a stable version of ubuntu, not ubuntu-latest which can
change unexpectedly. This switches all the other (non-test) workflows to
use ubuntu-22.04
@bcl bcl requested a review from a team as a code owner February 11, 2025 18:27
@bcl bcl requested review from mvo5, thozza, schuellerf and ondrejbudai and removed request for a team February 11, 2025 18:27
@bcl bcl changed the title Main ubuntu 22.04 Switch github workflows to ubuntu 22.04 Feb 11, 2025
Copy link
Member

@achilleas-k achilleas-k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Copy link
Contributor

@mvo5 mvo5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit of a meta-question (I guess its not very relevant for this PR but I'm curious): why do we pick ubuntu-22.04 instead of ubuntu-24.04 as the "stable" relase? AIUI ubuntu-latest points to ubuntu-24.04 since a few weeks [0].

The change itself looks fine and can be merged of course.
[0] actions/runner-images#10636

@bcl
Copy link
Contributor Author

bcl commented Feb 12, 2025

Ah, didn't realize latest was already on 24 (I pay almost zero attention to ubuntu releases), but I picked 22.04 out of the hat :) It's the next stable release after 20.04 according to github's list in the email I got.

We can also jump to 24.04 if we want.

@mvo5
Copy link
Contributor

mvo5 commented Feb 12, 2025

Ah, didn't realize latest was already on 24 (I pay almost zero attention to ubuntu releases), but I picked 22.04 out of the hat :) It's the next stable release after 20.04 according to github's list in the email I got.

We can also jump to 24.04 if we want.

No strong preference here, I was just curious about the choice.

@schuellerf
Copy link
Contributor

Why not use "latest"? Do we have a reason to pin to a specific version?
This way we automatically get updates and if there are problems with the actions we need to fix them anyway…

@thozza
Copy link
Member

thozza commented Feb 12, 2025

Why not use "latest"? Do we have a reason to pin to a specific version? This way we automatically get updates and if there are problems with the actions we need to fix them anyway…

Generally, we pin things in CI to keep it stable and know the reason for a potential failure. If the underlying infra changes automatically and causes the CI to fail, you may wonder if it is related to the PR. And when we update things related to CI infrastructure, we can be sure that the failure is related to that change.

@thozza thozza merged commit 74638a9 into osbuild:main Feb 12, 2025
46 of 51 checks passed
@schuellerf
Copy link
Contributor

@thozza I'm not sure if I get the "pin things in CI" thing with sudo apt-get update ;)

run: sudo apt-get update

@achilleas-k
Copy link
Member

@thozza I'm not sure if I get the "pin things in CI" thing with sudo apt-get update ;)

run: sudo apt-get update

That just pulls in repo metadata so we can apt install the dependencies.

Dependency version changes during an LTS release is unlikely to cause issues (though not impossible). The distro release changing from under your feet however can bring much larger package changes (major versions, even package names can change).

@bcl
Copy link
Contributor Author

bcl commented Feb 12, 2025

The original thoughts on this are in commit e8ae7e7 and I read that as trying to keep it from jumping to a new version of the os, not pinning every last package.

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.

5 participants