-
Notifications
You must be signed in to change notification settings - Fork 113
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
Tracking Issue: Improve CI #188
Closed
5 tasks done
Labels
ci
Everyting related to CI (Continuous integration)
Comments
@citizen-stig Suggests that |
Merged
Some tips recommended by @bkolad : |
Also there were some comments in #439 in description |
@neysofu you might be interested in this one. |
This was referenced Jul 28, 2023
Merged
I would propose we close this –it's outdated at this point– and create single issues for more specific improvements we want to make. |
Agreed. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Comprehensiveness
check
first, and other jobs run only if it succeeds. So if PR is completely broken, not a lot of resources will be wasted.Performance
CI runtime has gone from 30 minutes to 10 minutes. (Thanks @citizen-stig for switching to
sccache
in #197). We would like to reduce this time even further.Some Ideas (TODO: expand, evaluate tradeoffs)
trybuild
so that they can build in parallel with other items instead of sequentially.Thanks @bkolad for the suggestion
The text was updated successfully, but these errors were encountered: