Cannot uninstall bundler in order to change the bundler version for ruby build #8717
Comments
|
it looks like bundler is included as a default gem for ruby 2.3.3 on travis here
but i'm not sure why. |
|
It seems 2.3.4 & 2.4.1 also have gem issues with bundler. See https://travis-ci.org/MSP-Greg/travis-ruby/builds/298359169 |
|
The default bundler install seems weird too, I personally only have an |
|
Got the same issue when trying to use bundler with lower version. I fixed that by downgrade before_install:
- rvm implode --force
- \curl -sSL https://get.rvm.io | bash -s 1.27.0
- rvm reload
- rvm install 2.2.3
- gem uninstall -i /home/travis/.rvm/gems/ruby-2.2.3 bundler -x
- gem install bundler -v 1.12.5 |
|
Another strategy I've found effective is to remove the entry under before_install:
- "find /home/travis/.rvm/rubies -wholename '*default/bundler-*.gemspec' -delete"
- gem install bundler --version $BUNDLER_VERSIONHacky and bothersome, but some day I won't be testing against a Vagrant dependency that is chained to specific versions of Bundler... |
Use the workaround from travis-ci/travis-ci#8717 (comment) to remove the default bundler gemspec from RVM. This fixes issues with the regression tests resolving to the incorrect bundler, cauing this error with the 2.5.0 RVM: 1) regression test with cookbook users should match expected output Failure/Error: command("git clone -q https://github.com/chef-cookbooks/#{name}.git .") Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1' ---- Begin output of bundle exec git clone -q https://github.com/chef-cookbooks/users.git . ---- STDOUT: STDERR: /home/travis/.rvm/gems/ruby-2.5.0/bin/bundle:23:in `load': cannot load such file -- /home/travis/.rvm/rubies/ruby-2.5.0/lib/ruby/gems/2.5.0/gems/bundler-1.16.1/exe/bundle (LoadError) from /home/travis/.rvm/gems/ruby-2.5.0/bin/bundle:23:in `<main>' from /home/travis/.rvm/gems/ruby-2.5.0/bin/ruby_executable_hooks:15:in `eval' from /home/travis/.rvm/gems/ruby-2.5.0/bin/ruby_executable_hooks:15:in `<main>' ---- End output of bundle exec git clone -q https://github.com/chef-cookbooks/users.git . ---- Ran bundle exec git clone -q https://github.com/chef-cookbooks/users.git . returned 1 # ./vendor/bundle/ruby/2.5.0/gems/mixlib-shellout-2.3.2/lib/mixlib/shellout.rb:293:in `invalid!' # ./vendor/bundle/ruby/2.5.0/gems/mixlib-shellout-2.3.2/lib/mixlib/shellout.rb:280:in `error!' # ./vendor/bundle/ruby/2.5.0/gems/rspec-command-1.0.3/lib/rspec_command.rb:111:in `block in command' # ./vendor/bundle/ruby/2.5.0/gems/rspec-command-1.0.3/lib/rspec_command.rb:108:in `tap' # ./vendor/bundle/ruby/2.5.0/gems/rspec-command-1.0.3/lib/rspec_command.rb:108:in `command' # ./spec/regression/regression_spec.rb:11:in `block (4 levels) in <top (required)>' # ./vendor/bundle/ruby/2.5.0/gems/rspec-command-1.0.3/lib/rspec_command.rb:47:in `block (2 levels) in <module:RSpecCommand>' # ./vendor/bundle/ruby/2.5.0/gems/rspec-command-1.0.3/lib/rspec_command.rb:45:in `block in <module:RSpecCommand>'
|
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 24 hours. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues |
* Use #is_a_path? conditionally on Bundler version * Use Bundler::VERSION * Update setting Bundler to frozen with #set_local * Force travis to install with correct Bundler version * Resolve rubocop offenses * Verify bundler version is not greater than 1.14.0 in travis * Print the version * Override install properly * Overwrite script as well * Force uninstall of bundler as suggestion in link https://stackoverflow.com/questions/26481650/travis-could-not-find-bundler-1-7-4 * try moving it to before_install * Try another tactic found on this travis-ci issue travis-ci/travis-ci#8717 (comment) * Turn condition in Gemfile into Bundler version log * Create build matrix with multiple Ruby & Bundler versions * Remove logging that creates test failures * Fix wrong bundler version * Add 2 more Bundler versions * Use matrix of 1 Ruby & 2 Bundler versions * Use Gem::Version to compare Bundler versions * Use #respond_to? instead of looking at Bundler * Remove duplication from #path?
This issue travis-ci/travis-ci#8717 helped to bypass default bundler version.
…teriores Solução sugerida em: travis-ci/travis-ci#8717 (comment)
Trying this solution to the default gem problem: travis-ci/travis-ci#8717 (comment)
Trying this solution to the default gem problem: travis-ci/travis-ci#8717 (comment)
Uninstalling bundler with the following command fails
rvm @global do gem uninstall bundler
the error message is
my build is on ruby 2.3.3, rvm 1.29.2, and rubygems 2.7.1.
i know that bundler will be a default gem in ruby 2.5.0 and above, but since i am using ruby 2.3.3 i would expect this to work.
The text was updated successfully, but these errors were encountered: