Reorganize Ubuntu CI actions - #6077
Merged
Merged
Conversation
Contributor
|
Test this please |
ye-luo
enabled auto-merge
July 31, 2026 16:19
ye-luo
approved these changes
Jul 31, 2026
Contributor
Author
|
I will update the branch protections so this can be merged ahead of #6058 and the results verified today. EDIT: Done. All 14 "linux" rules now point to their ubuntu* equivalents. |
This file contains hidden or 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
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.
Proposed changes
This PR restructures the GitHub actions CI but does not change any of the jobs that are run.
Insteaed of grouping many of the runs under "linux", they are now grouped by OS (ubuntu22, ubuntu24). This was already done for macos and centos10.
The ubuntu24 and centos10 specs are also simiplified -- there should be no need to specify the same container for every job.
Provided this works, a subsequent PR will add some ubuntu26 configurations with appropriate updates to run_step.sh also included.
In order to be merged, we will have to update the branch protections due to the new names. Will do so after addressing any review suggestions and feedback.
What type(s) of changes does this code introduce?
Does this introduce a breaking change?
What systems has this change been tested on?
None.
Checklist