Update CI to Fedora 41, disable updates by default #3464
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We basically always want to run the latest stable release, but the newer the release the more update churn there is, and that sort of instability is bad for CI. To counter that, disable updates by default. If and when we need specific updates to components, we now do it explicitly. This seems like the best of both worlds really. Technically this is two different changes, one to bump the Fedora version and another to disable updates, but if they are separated then time goes backwards for that one commit so I think it's better to just have this as one commit.
|
Indeed, and oh, good point about disabling the "updates" repo as well (something that's easy to forget 😄) |
|
This also gives us better reproducibility of test failures in CI, hopefully, since we can now compare (or even pull) the image ID locally. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We basically always want to run the latest stable release, but the newer the release the more update churn there is, and that sort of instability is bad for CI. To counter that, disable updates by default. If and when we need specific updates to components, we now do it explicitly. This seems like the best of both worlds really.
Technically this is two different changes, one to bump the Fedora version and another to disable updates, but if they are separated then time goes backwards for that one commit so I think it's better to just have this as one commit.