Refactor #17011

Allow override of BUNDLER_CMD in foreman-rake

Added by Dominic Cleal 11 months ago. Updated 11 months ago.

Status:Closed
Priority:Normal
Assigned To:Michael Moll
Category:rake tasks
Target version:-
Difficulty: Bugzilla link:
Found in release:1.12.1 Pull request:https://github.com/theforeman/foreman/pull/3675
Story points-
Velocity based estimate-
Release1.14.0Release relationshipAuto

Description

Allow BUNDLER_CMD in foreman-rake script to be set from a build script, then not overridden when a Gemfile is present. Currently this line overrides it:

[ -f Gemfile ] && && BUNDLER_CMD="bundle exec"

but for some OSes (i.e. Ubuntu 14.04) it should be overridden during build to use a particular Ruby binary.


A user on IRC did hit this:

foreman-rake uses the wrong ruby: Notice: /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: /opt/puppetlabs/puppet/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- bundler (LoadError)


Related issues

Copied from Packaging - Bug #15834: foreman-rake doesn't use foreman-ruby Closed 07/25/2016

Associated revisions

Revision 91cfc0ca
Added by Michael Moll 11 months ago

fixes #17011 - refactor BUNDLER_CMD in foreman-rake

History

#1 Updated by Dominic Cleal 11 months ago

  • Copied from Bug #15834: foreman-rake doesn't use foreman-ruby added

#2 Updated by Dominic Cleal 11 months ago

  • Status changed from Assigned to Ready For Testing

#3 Updated by Michael Moll 11 months ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by Dominic Cleal 11 months ago

  • Release set to 1.14.0

Also available in: Atom PDF