Has anyone established a pattern to use go to build a rails project that uses bundler? Using a job that simply does the default rake actions gets a "Could not find gemname-1.2.3 in any of the sources" message.
I can run 'bundle install' outside of go in order to get the required gems installed on the box. I'd prefer though, to have something in go that addresses this step. Is it enough to have an earlier stage that runs 'bundle install' in a shell? Or, an earlier task within the same job?
Thanks for any thoughts!
Dave
Comments
1 comment
Here's what we're doing as part of a rails3 project:
Once the environment is using the script, use the exec task to shell out to RAILS_ROOT/vendor/ruby/1.8/bin/[rake|rcov|whatever]
-- Ketan
studios.thoughtworks.com| twitter.com/ketanpkr
Please sign in to leave a comment.