CI: Add cache action to preserve build artifacts. #417
Conversation
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
Github Copilot made this... so who knows if it actually works.
Owner
|
That's such a good idea, I didn't know Github Actions CI support caching! :) |
Owner
|
I will address the --all-features in a follow up commit |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Right now CI rebuilds from scratch for each step. It takes way longer than it needs to. This action supposedly will cache the build artifacts so they can be re-used each step.
Note
Github Copilot made this... so who knows if it actually works.
To Do
cargo build --all-featuresor something first, then run everything else afterwards? What's the most optimal way?