Better gem caching for preview deploys #2171
Merged
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.
What are you trying to accomplish?
We have three different gemfiles that install gems for 1) the lib, 2) the demo app, and 3) the Kuby deploy. Right now, we're only caching gems for the lib.
Integration
No changes necessary in production.
Risk Assessment
What approach did you choose and why?
This PR adds several additional ruby/setup-ruby steps for the other two gemfiles. Including this action multiple times seems to be ok and takes care of a lot of the difficult minutiae of caching bundles.
Accessibility