Allow a cache restore when stack.yaml changes #29
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.
Using the
stack.yamlcontents as the sole cache key for dependencies makes sense when the vast majority of changes tostack.yamlare resolver upgrades that are going to necessitate rebuilding everything. It makes less sense when we're changingstack.yamljust to do an upgrade of a single dependency. For that sort of change, CI can make use of a previous cached dependency set and save (in the case of megarepo/backend) around an hour of rebuilding.This change allows a build to restore any dependency cache that is for the same GHC version.