Project

General

Profile

Actions

Refactor #17011

closed

Allow override of BUNDLER_CMD in foreman-rake

Added by Dominic Cleal over 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Rake tasks
Target version:
Difficulty:
Triaged:
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 1 (0 open1 closed)

Copied from Packaging - Bug #15834: foreman-rake doesn't use foreman-rubyClosed07/25/2016Actions
Actions #1

Updated by Dominic Cleal over 7 years ago

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

Updated by Dominic Cleal over 7 years ago

  • Status changed from Assigned to Ready For Testing
Actions #3

Updated by Anonymous over 7 years ago

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

Updated by Dominic Cleal over 7 years ago

  • translation missing: en.field_release set to 189
Actions

Also available in: Atom PDF