Heroku environment variables

[quarterdome]

Trying to use BigTuna for CI of a RailsApp on Heroku. Made it work using GIT_SSH workaround, but now am stuck on a the first step: "bundle install" inside the build script.

Fetching source index for http://rubygems.org/

sudo: must be setuid root
sudo: must be setuid root
/usr/ruby1.9.2/lib/ruby/1.9.1/rubygems/format.rb:38:in from_file_by_path': Cannot load gem at [/usr/ruby1.9.2/lib/ruby/gems/1.9.1/cache/rake-0.8.7.gem] in /app/tmp/flagship/build_3_20110415165235 (Gem::Exception) from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/source.rb:72:infetch'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/installer.rb:45:in block in run' from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/spec_set.rb:12:inblock in each'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/spec_set.rb:12:in each' from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/spec_set.rb:12:ineach'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/installer.rb:44:in run' from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/installer.rb:8:ininstall'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/cli.rb:225:in install' from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/vendor/thor/task.rb:22:inrun'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/vendor/thor/invocation.rb:118:in invoke_task' from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/vendor/thor.rb:246:indispatch'
from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/vendor/thor/base.rb:389:in start' from /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/bin/bundle:13:in<top (required)>'
from /usr/ruby1.9.2/bin/bundle:19:in load' from /usr/ruby1.9.2/bin/bundle:19:in

'

I am sure that can be fixed with proper settings of environment variables, but not sure where to start. Very much appreciate any help.

BigTuna rocks!

[leckylao]

I have the same issue on running Integrity on Heroku. I hacked around this by putting the required gem on the CI Gemfile.....