RVM, bundler and hudson configuration

[tommy chheng]

I'm having an issue with hudson, RVM and bundler.

I have two ruby apps(lets call, A and B) listed on hudson.
A is running fine with hudson.
When I try to run B on hudson, it tries to use A's rvm gempath.
In the Execute Shell Script, I have:
rvm use 1.9.2 && rvm gemset use project_B && bundle install

But in the console output, it says:
Your bundle was installed to `/usr/local/rvm/gems/ruby-1.9.2-
p0@project_A`

Why is project_A's env variable for the gempath interfering?

[Darcy Laycock]

Since it doesn't look like you're sourcing rvm inside the shell
script, it's most
likely calling rvm as a binary (vs. shell function) hence it doesn't
actually execute
it.

The solutions are:
- make the shebang "#!/usr/bin/env rvm-shell 1.9.2"
- use "rvm 1.9.2 exec bundle install"
- make the shebang "#!/bin/bash", source "/usr/local/rvm/scripts/rvm"
and use the above after that.

Or, wait until I write a plugin that lets you just pass in the ruby
string + the shell command :P

[lusis]

I run it like so:

step #1 -
#!/bin/bash -l
rvm use 1.8.7
rvm gemset create ${BUILD_TAG}
rvm gemset use ${BUILD_TAG}
gem install bundler --pre
bundle install
bundle check

step #2 -
#!/bin/bash -l
rvm use 1.8.7@${BUILD_TAG}
bundle exec rake test

step #3 -
#!/bin/bash -l
rvm use 1.8.7@${BUILD_TAG}
bundle exec rake hudson:coverage:unit

step #4 -
#!/bin/bash -l
rvm use 1.8.7
rvm --force gemset delete ${BUILD_TAG}

I have build plans for each of the ruby vms. Step 3 only applies to
mri 1.8.7 because of bugs in rcov. The rest are just steps 1,2,4 with
the version changed.

[lusis]

I've actually just been putting #!/bin/bash -l in my hudson steps for
now. Works great. Then I generate a new gemset based on the jobname
variable and run bundle install. Final step in the job destroys the
gemset.

[Tommy Chheng]

I'm trying this as one script in hudson:
#!/bin/bash -l
source "/usr/local/rvm/scripts/rvm"
rvm use ruby-1.9.2

rvm gemset create ${BUILD_TAG}

rvm gemset use ruby-1.9.2@${BUILD_TAG}
gem install rake

gem install bundler --pre
bundle install
bundle check

bundle exec rake test

The output is:

info: Using ruby 1.9.2 p0

info: Gemset 'hudson-project-56' created.
 [31mCould not find rake-0.8.7 in any of the sources [0m

I'm sure rake is installed. It looks like it's not using the right gemset?

Any ideas?

[Darcy Laycock]

Just to confirm - the hudson user is a member of the rvm group?
If not, that may be an issue.

Try using a script like:

#!/bin/bash -l
source "/usr/local/rvm/scripts/rvm"
rvm use ruby-1.9.2@${BUILD_TAG} --create

gem install rake
gem install bundler --pre
bundle install
bundle check
bundle exec rake test

The use-style syntax is faster + our preferred syntax fwiw.

> >> rvm use 1.9.2&&  rvm gemset use project_B&&  bundle install

[lusis]

You shouldn't need to install rake. RVM installs it as part of the
base ruby vm unless something didn't work when you initially installed
it. I would try with 1.9.1 and also reinstall 1.9.2 just to make sure.

> >> rvm use 1.9.2&&  rvm gemset use project_B&&  bundle install

[Tommy Chheng]

Thanks, found the source of the error.

Somewhere in the configuration, RUBYOPT was being set to project A's
gempath even though I was running tests for project B.

I just export RUBYOPT="" and both hudson tests are working with RVM.

[lusis]

I was getting a similar problem initially. I just set my default to
system and the bash -l took care of the rest.