Appraisal with vendorized gems #30
Comments
|
We'd be happy to take a pull request that adds this functionality. |
|
I'm not sure where to begin though... keeping the same env variables results in an error saying the bundler specs have already been loaded. If you don't keep the env variables, it looks for the gems globally. |
|
I'm not sure what the fix is either. We have to run a new bundle command because we're switching gemfiles. We may just need to pass something else to that bundle command to make sure it uses |
phillbaker
added a commit
to phillbaker/appraisal
that referenced
this issue
Sep 28, 2013
Appraisal seems to require Bundler to install the requirements of the Gemfile in the global namespace, see thoughtbot#13 and thoughtbot#30.
sikachu
pushed a commit
that referenced
this issue
Mar 10, 2015
This fixes an issue where user would get "Could not find bundler" error when tries to use Appraisal in project that vendorize gems. The root cause was that Bundler will not bundle itself when you run `bundle install` with `--path` option. As Appraisal resets `GEM_HOME` to avoid dependency conflict, it also made RubyGems unable to locate code for Bundler as well. Fix #13, #30 and #87.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Related to #13, please allow support for vendorized gems. When using a Continuous Integration server (like Hudson or Jenkins), gems cannot be installed globally for a variety of reasons:
Note that #13 occurs when you install gems anywhere other than the default path. i.e. specifying
--pathin thebundleoption completely breaks appraisal...The issue happens because you're shelling out to the system another bundle command here.
The text was updated successfully, but these errors were encountered: