bundler install picks up wrong Gemfile

[mreinsch]

Since updating to 0.1.3, all builds fail because running "bundle install --path=%project_dir%/bundle --deployment" now somehow picks up bigtuna's Gemfile instead of the project's Gemfile. As a result, the project is missing the .bundle directory.

As a workaround for that I'm using: "bundle install --gemfile=%build_dir%/Gemfile --path=%project_dir%/bundle --deployment"

[mreinsch]

seems this is because Bundler.with_clean_env doesn't actually clean the environment:

Output of env includes (which it shouldn't):
RAILS_ENV=production
BUNDLE_GEMFILE=/srv/dep/bigtuna/current/Gemfile

[wuputah]

Duplicate of #51, and rubygems/bundler#900, which I have an open pull request (rubygems/bundler#1057) to fix.

Bundler.with_clean_env will still will not clean RAILS_ENV - it has nothing to do with Bundler. You should expect to set RAILS_ENV in your tests - Bigtuna does not know what RAILS_ENV (if any) you need for your tests. #44 will help making this easier.

[antekpiechnik]

We have tried resolving #44 in the shared_env branch.

[michalbugno]

Also: RAILS_ENV is cleared within steps so one has to explicitly set it in test (for example with "env RAILS_ENV=test command_to_run")