Fallback to cache-key Without Branch if Missing #28
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
This uses a cache-key for the initial build on branches until a cache key is generated specific to the branch.
|
Thank you @ksylvest, looks great. |
FelicianoTech
approved these changes
Jun 18, 2020
This was referenced Jun 23, 2020
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.
This uses a cache-key for the initial build on branches until a cache key is generated specific to the branch.
Motivation
Builds on new branches always install bundled dependencies without cache. This can be avoided since it is likely a cached version for the exact lockfile already exists.
Describe
Introducing a fallback key based solely on the lockfile.
Fixes #33.