Bundler fails on production with the plugin added

[juliancheal]

Speaking to @Fryguy he thinks this is a bundler issue, relating to that the plugin is not in the lock file.

Here is the output from my Heroku deploy

-----> Ruby app detected
-----> Installing bundler 1.17.3
-----> Removing BUNDLED WITH version in the Gemfile.lock
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-2.6.5
-----> Installing dependencies using bundler 1.17.3
       Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
       The dependency bundler-inject (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for  but the dependency is only for . To add those platforms to the bundle, run `bundle lock --add-platform `.
       Unable to find a spec satisfying bundler-inject (>= 0) in the set. Perhaps the
       lockfile is corrupted?
       Bundler Output: The dependency bundler-inject (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for  but the dependency is only for . To add those platforms to the bundle, run `bundle lock --add-platform `.
       Unable to find a spec satisfying bundler-inject (>= 0) in the set. Perhaps the
       lockfile is corrupted?
 !
 !     Failed to install gems via Bundler.
 !
 !     Push rejected, failed to compile Ruby app.
 !     Push failed

Moving plugin 'bundler-inject' to group :development do didn't fix this either as I get a NoMethodError: undefined method 'full_gem_path' for nil:NilClass as seen in this bundler issue rubygems/rubygems#3319 (comment)

[Fryguy]

We are also seeing something similar in the manageiq bot - ManageIQ/miq_bot#448 - specifically, https://travis-ci.org/github/ManageIQ/miq_bot/builds/663249302#L255

[Fryguy]

I'm going to close this one until we have a reproducer - I haven't seen it in years.