Explicitly use .yarn directory as cache directory #1090
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
This saves caching the whole of `node_modules`, but still provides a performance improvement to builds, as an offline cache can be used. The default cache location isn't persisted by GitLab
|
Looks like the deploy fails are unrelated to this PR:
|
|
I'm not sure why you're suggesting not to cache node_modes, not having to fetch for subsequent builds still seems useful to me |
|
In my experience This also matches how GitLab recommend caching for NPM directly: https://docs.gitlab.com/ee/ci/caching/#caching-nodejs-dependencies |
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 saves caching the whole of
node_modules, but still provides a performance improvement to builds, as an offline cache can be used.The default cache location isn't persisted by GitLab