-
Notifications
You must be signed in to change notification settings - Fork 396
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
github: clean up and consolidate the build matrix #5598
Conversation
This also contains an update to use macOS-14 on ARM to build x86 binaries to keep the build matrix more regular. It's still faster than Windows. :') I can pull that out, but I think migrating off macos-13 is probably a good idea in general. |
64ae60d
to
33960d5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for working on this!
f37007d
to
0249c77
Compare
Signed-off-by: Austin Seipp <[email protected]>
Signed-off-by: Austin Seipp <[email protected]>
This makes the methods and the madness a little more consistent with each other, so it's easier to read and categorize build reports in the GHA UX. No functional change, but requires updating rulesets upstream. Signed-off-by: Austin Seipp <[email protected]>
There's no real reason to keep these separate and it makes the build UX easier to navigate, too; as well as see what the actual "global" slowest builds across all workflows easier to see. Signed-off-by: Austin Seipp <[email protected]>
Just a rename; now that `build` and `build-nix` are unified, this makes it more clear this workflow is conceptually separate. NFC. Signed-off-by: Austin Seipp <[email protected]>
Moves all the Windows junk out of the way, where it can be encapsulated. Signed-off-by: Austin Seipp <[email protected]>
'ci' is much more high-level and accurately explains what the jobs in this test should be for. It's much more applicable than 'test' (testing what? on what platforms?) or 'build' (does it only build? or test? or run linters?) Signed-off-by: Austin Seipp <[email protected]>
The CI system is variously hitting the limits of the existing 15 minute build mark; in particular, Windows seems to be consistently hitting ~14m so the chance of a runner timing out gets high if the underlying load is also high. While I'm working on this, let's just (regrettably) increase the slack on the timeout so that everyone else isn't disturbed. Signed-off-by: Austin Seipp <[email protected]>
0249c77
to
0a9f96c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, at a glance. Thank you!
This makes the existing build matrix much more "regular" and makes it easier to navigate by consolidating everything under the main build workflow. Here's an example of the results: https://github.com/jj-vcs/jj/actions/runs/13180977716
This requires a mass rename of all the required checks, so @martinvonz will have to take over.
Checklist
If applicable:
CHANGELOG.md