Enable caching of busser gems only if we are in a test-kitchen run #78
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.
This is a hack-like workaround to limit caching of the generic busser gems cache to occasions when we are running as part of a test-kitchen run.
We use
Dir.pwd
to guess whether we are in a kitchenci generated directory and thus can assume we are running in a kitchenci run with the kitchen-vagrant plugin.Why doing this? Because