Project

General

Profile

Refactor #17011

Allow override of BUNDLER_CMD in foreman-rake

Added by Dominic Cleal about 2 years ago. Updated 4 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
rake tasks
Target version:
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

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-rubyClosed2016-07-25

Associated revisions

Revision 91cfc0ca (diff)
Added by Michael Moll about 2 years ago

fixes #17011 - refactor BUNDLER_CMD in foreman-rake

History

#1 Updated by Dominic Cleal about 2 years ago

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

#2 Updated by Dominic Cleal about 2 years ago

  • Status changed from Assigned to Ready For Testing

#3 Updated by Michael Moll about 2 years ago

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

#4 Updated by Dominic Cleal about 2 years ago

  • Legacy Backlogs Release (now unused) set to 189

Also available in: Atom PDF