Open wolfeidau opened 12 years ago
+1.
I seem to be having a problem with subsequent bundle exec rake tasks finding vendor/bundle.
This doesn't mention anything about a need to configure that path in subsequent tasks...
http://blogs.atlassian.com/2012/06/building-ruby-projects-with-bundler-and-the-bamboo-ruby-plugin/
It seems to be injecting from the .rvmrc? instead of finding ./vendor/bundle: GEM_PATH=/home/apps/.rvm/gems/ruby-2.0.0-p195
I'm not clear where this needs to change in our configuration.
So, I'm still looking, but it seems that I'm mixing RVM and the bundler path for gemsets. Since we want to both build the "master" and "develop" branch without modifying the .rvmrc and without co-mingling gemsets, we definitely want our gemsets stored in a build-plan specific way.
I also don't want to remove .rvmrc from our repository.
Am I understanding this correctly so far?
Once you have added a rake task and selected a ruby runtime I want to ensure subsequent rake tasks read this and set it as the default value.
This will just remove a little repetition when configuring a few tasks.