CI refactor: use install-action & cargo-hack #654
Draft
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
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.
cargo-hack
I recently discovered cargo-hack which has the powerful (😉) feature of
--feature-powerset, which allows easy testing of all possible combinations of features. This has two main benefits compared to what we are doing now:install-action
install-action, maintained by the same developer, is a convenient way to install tools like cross and cargo-hack.
Problems
Currently cargo-hack does not seem to support keeping the compiled artifacts for each run, which means we will be losing some functionality in our CI. This is why this PR is still a draft. I have submitted an issue to ask about this.