You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are no clear examples of how to best cache installed dependencies using rushjs. It would be a boon to both rushstack and developers to be able to check the framework repo's ci.yml to see how to implement a primitive for CI operations.
Repro steps
Repro steps not needed
Details
See summary
Standard questions
Please answer these questions to help us investigate your issue more quickly:
QnA unneeded.
The text was updated successfully, but these errors were encountered:
It'd probably be pretty straightforward to cache the common/temp/node_modules and common/temp/*/node_modules (for subspaces) folders using the GitHub Actions cache. Dependency install happens pretty quickly in our CI, so we haven't investigated that yet, but if you want to put together a proposed change, we'd probably take it.
Right now we've mostly been investigating using the GitHub Actions cache for builds (see related issue actions/toolkit#1760).
Summary
There are no clear examples of how to best cache installed dependencies using rushjs. It would be a boon to both rushstack and developers to be able to check the framework repo's ci.yml to see how to implement a primitive for CI operations.
Repro steps
Repro steps not needed
Details
See summary
Standard questions
Please answer these questions to help us investigate your issue more quickly:
QnA unneeded.
The text was updated successfully, but these errors were encountered: