-
Notifications
You must be signed in to change notification settings - Fork 101
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
Allow multiple cache keys #157
Comments
Bump. Same here. Our company uses React on Rails and we were trying to use this orb to update our circle configuration. We cache our gems as well and our yarn dependencies in separate caches so we're not currently able to grab the cache-keys for the multiple caches we have. |
I would love someone to implement this, because I am not sure how it would work - don't you need to implement different paths to cache, for example? |
We have a need for this as well. @bahmutov is it possible to simply expose Circle's native |
You can look at the src/orb.yml to see how to implement this, maybe it’s not too bad
…Sent from my iPhone
On Jun 5, 2020, at 12:19, Alexander Tsepkov ***@***.***> wrote:
We have a need for this as well. @bahmutov is it possible to simply expose Circle's native save_cache and restore_cache parameters directly? That would handle multiple keys as well as multiple paths.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Slightly different, but due to the cache key inflexibility, it's also preventing developers from using fallback cache keys to improve the cache hit rate and improve build times further. For example, the node orb allows this: |
We are exploring this orb for a Rails and Vue app.
bundle
for gems can take quite a while since we have some native gems that require a build process. Unfortunately, with this orb, there does not seem to be any way to use the bundler cache that we produce as part of our workflow.I imagine the feature would look like this:
The text was updated successfully, but these errors were encountered: