Articles in this section

See more

Pattern for using go to build a rails project that uses bundler?

Avatar
Dave Cameron
Updated
Follow 

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

Sort by Date Votes
  • Avatar
    Ketan Padegaonkar
    Dave,

    Here's what we're doing as part of a rails3 project:


    • Run "bundle pack" to copy over all .gem files to RAILS_ROOT/vendor/cache as per the Gemfile.lock. This is the only dir that needs to go into source control. The unpacked gems inside vendor dir need not.

    • Copy over the bundler.gem file to RAILS_ROOT/vendor/cache (required for next step)

    • As part of the each CI job, we have a script that unpacks bundler into the correct dir and unpacks the rest of the gems using bundler


    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



    0
    Permalink

Please sign in to leave a comment.