accelerate CI via cargo binstall#578
Open
plebhash wants to merge 2 commits into
Open
Conversation
4da8290 to
094c977
Compare
094c977 to
ecd565f
Compare
Member
|
@plebhash can you rebase this? And can you also squash the commits (kinda similar changes) |
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.
accelerate CI via
cargo-binstallinstead of compiling
cargo-nextestandcargo-semver-checkson every run, we install pre-built binaries viacargo-binstall.additional hardening:
quick-installto only use upstream release artifacts (instead of third-party quick-install artifacts)GITHUB_TOKENtocargo-binstallto avoid unauthenticated GitHub API rate-limit fallback--lockedfor deterministic fallback behavior if source install is ever neededestimated impact (latest successful PR run vs median of 5 recent comparable successful PR runs on the same workflows/jobs):
ci (ubuntu-latest):~2m34s -> ~3s(~98% reduction)~32m18s -> ~28m41s(~3m37s faster, ~11%)ci (macos-latest):~2m38s -> ~5s(~97% reduction)~31m57s -> ~30m04s(~1m53s faster, ~6%)semver-check:~5m09s -> ~4s(~99% reduction)~15m04s -> ~9m44s(~5m20s faster, ~35%)critical-path wall clock also improves (
~32m18s -> ~30m04s, ~2m14s), while matrix jobs still run in parallel.