Skip to content
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

Enable caching of busser gems only if we are in a test-kitchen run #78

Merged
merged 4 commits into from
Mar 31, 2015

Conversation

tknerr
Copy link
Owner

@tknerr tknerr commented Feb 3, 2015

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

  1. we only need it in this case and
  2. it alleviates problems with windows guests (see Windows Guest Support for Generic Bucket (and others too?) fgrehm/vagrant-cachier#137)

@tknerr
Copy link
Owner Author

tknerr commented Mar 31, 2015

Also added compatibility with test-kitchen 1.4, see test-kitchen/test-kitchen#677 (comment)

@tknerr
Copy link
Owner Author

tknerr commented Mar 31, 2015

Also changed the cached directory to /tmp/busser|verifier/gems/cache - otherwise we would never get an updated busser version itself according to this.

tknerr added a commit that referenced this pull request Mar 31, 2015
Enable caching of busser gems only if we are in a test-kitchen run
@tknerr tknerr merged commit bc2c090 into master Mar 31, 2015
@tknerr tknerr deleted the busser-caching branch August 7, 2015 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant