Skip to content

bundle exec fails on Bundler 2 with config path and deployment #6349

@eregon

Description

@eregon

Environment Information

Provide at least:

  • JRuby version: jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 25.262-b10-jvmci-20.2-b03 on 1.8.0_262-b10 +jit [linux-x86_64]

Expected Behavior

It works, like on CRuby.

Actual Behavior

gem install bundler:2.1.4
git clone --branch debug https://github.com/eregon/memo_wise.git
cd memo_wise
bundle config --local deployment true
bundle config --local path vendor/bundle
bundle install --jobs 4
...
$ bundle exec rubocop -h 
bundler: failed to load command: rubocop (/home/eregon/code/memo_wise/vendor/bundle/jruby/2.5.0/bin/rubocop)
Gem::Exception: can't find executable rubocop for gem rubocop. rubocop is not currently included in the bundle, perhaps you meant to add it to your Gemfile?
  /home/eregon/.rubies/jruby-9.2.12.0/lib/ruby/gems/shared/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:374:in `block in find_spec_for_exe'
  /home/eregon/.rubies/jruby-9.2.12.0/lib/ruby/gems/shared/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:402:in `block in activate_bin_path'
  /home/eregon/code/memo_wise/vendor/bundle/jruby/2.5.0/bin/rubocop:23:in `<main>'
  org/jruby/RubyKernel.java:1009:in `load'
zsh: exit 1     bundle exec rubocop -h

From ruby/setup-ruby#72.
This means JRuby doesn't work in ruby/setup-ruby with bundler-cache: true and an existing Gemfile.lock.

Maybe related to #6053 ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions