Cache build artifacts using rust-cache
#399
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
The builds using the stable Rust channel will see the biggest benefits from this since the cache will remain valid for weeks at a time. However, when multiple builds are made in a single day, the cache for nightly Rust will also be helpful.
mgeisler
added a commit
that referenced
this pull request
Jun 27, 2021
GitHub will run up to 20 jobs in parallel, so can get faster builds by running jobs in parallel. With the extensive caching we use, this should result in about the same load for GitHub. Together with #399, this brings the time down to 1.5 minutes, removing about 2 minutes from every PR.
mgeisler
added a commit
that referenced
this pull request
Jun 27, 2021
GitHub will run up to 20 jobs in parallel, so can get faster builds by running jobs in parallel. With the extensive caching we use, this should result in about the same load for GitHub. Together with #399, this brings the time for running all tests down to 1.5 minutes, removing about 2 minutes from every PR.
mgeisler
added a commit
that referenced
this pull request
Jun 27, 2021
GitHub will run up to 20 jobs in parallel, so can get faster builds by running jobs in parallel. With the extensive caching we use, this should result in about the same load for GitHub. Together with #399, this brings the time for running all tests down to 1.5 minutes, removing about 2 minutes from every PR.
mgeisler
added a commit
that referenced
this pull request
Jun 27, 2021
GitHub will run up to 20 jobs in parallel, so can get faster builds by running jobs in parallel. With the extensive caching we use, this should result in about the same load for GitHub. Together with #399, this brings the time for running all tests down to 1.5 minutes, removing about 2 minutes from every PR.
mgeisler
added a commit
that referenced
this pull request
Jun 27, 2021
GitHub will run up to 20 jobs in parallel, so can get faster builds by running jobs in parallel. With the extensive caching we use, this should result in about the same load for GitHub. Together with #399, this brings the time for running all tests down to 1.5 minutes, removing about 2 minutes from every PR.
mgeisler
added a commit
that referenced
this pull request
Jun 27, 2021
GitHub will run up to 20 jobs in parallel, so we can get faster builds by running more jobs in parallel. With the extensive caching we use, this should result in about the same load for GitHub. Together with #399, this brings the time for running all tests down to 1.5 minutes, removing about 2 minutes from every PR.
Merged
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.
No description provided.