-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use yarn cache on local and RA #279
base: master
Are you sure you want to change the base?
Conversation
only: | ||
variables: | ||
- $THEME_PATH | ||
- $YARN_CACHE_FOLDER |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line should be removed imho, cause front jobs should be triggered only by theme defined, and nothing else (currently front job will try to run even if theme is not initialized yet, because YARN_CACHE_FOLDER is defined)
- web/themes/custom/XXX/package.json # ... this path has to be hardcoded | ||
- web/themes/custom/XXX/yarn.lock # ... this path has to be hardcoded | ||
paths: | ||
- ${THEME_PATH}/node_modules/ # Populated during yarn install |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see reason to move this to "only_var_theme" anchor
Can you please explain motivation ?
@@ -53,6 +56,7 @@ front-build: | |||
docker pull $(IMAGE_FRONT); \ | |||
$(call frontexec, node -v); \ | |||
$(call frontexec, yarn -v); \ | |||
$(call frontexec, yarn install --ignore-optional --check-files --prod); \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bad idea to keep it in the same dir as theme
Speed up front jobs both on local and gitlab CI by keeping yarn cache in local directory