You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expected this project worked on Bundler, as I saw Gemfile on the project.
$ ruby -v
ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
$ bundle install --path vendor/bundle
$ bundle exec rake -T
bundler: failed to load command: rake (/usr/local/ruby-2.7.1/bin/rake)
Gem::Exception: can't find executable rake for gem rake. rake is not currently included in the bundle, perhaps you meant to add it to your Gemfile?
/usr/local/ruby-2.7.1/lib/ruby/2.7.0/bundler/rubygems_integration.rb:374:in `block in replace_bin_path'
/usr/local/ruby-2.7.1/lib/ruby/2.7.0/bundler/rubygems_integration.rb:402:in `block in replace_bin_path'
/usr/local/ruby-2.7.1/bin/rake:23:in `<top (required)>'
I already don't remember precisely, but I think that Travis is using Bundler to install dependencies. That is the only use case I have for Bundler. I don't see any other reason why it should be used to execute the test suite. If there is other way to install dependencies on Travis, I might consider removing Gemfile.
I don't see any other reason why it should be used to execute the test suite. If there is other way to install dependencies on Travis, I might consider removing Gemfile.
It's okay not to do it. The merit to use bundler is you can test abrt-ruby with the specific version or the latest version's rspec and rake, sharing developers the reproducing way through Gemfile relatively easiler. But the demerit for using Bundler might make the more complexity for this project.
I expected this project worked on Bundler, as I saw
Gemfile
on the project.Do you have a reason not to do like this?
The text was updated successfully, but these errors were encountered: