Make the Gems cache directory configurable. #3012
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
added 2 commits
April 22, 2014 12:25
This directory can be set using the --gems-cache option when configuring Rubinius. Using this option one can move the Gems cache directory out of the local working tree if needed. This in turn means CI systems that wipe the local working tree don't have to constantly re-download the same Gems. Considering this in itself takes time and RubyGems doesn't always respond this can save quite the time in a build process. The trade off is that you'll have to, once in a while, prune this directory to prevent it from ever growing in size. Corresponding issue: #3011
This somehow sneaked in. I swear this never happens to me.
brixen
added a commit
that referenced
this pull request
May 7, 2014
Make the Gems cache directory configurable.
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.
See #3011 and the commits for more info. This should be good to go but before this gets merged I'd like a second pair of eyes from @brixen and @dbussink. I also want to wait on Travis to see if I broke anything severe ("works on my box").