On Wed, Jul 14, 2010 at 8:29 AM, Todd Sedano <[email protected]> wrote: > > I'm switching to Bundler for a rails 2.3 project. Is there anything magical > that I should do on my CI machine? I did do a "sudo gem install bundler." > I'm guessing that I want to do a "bundle install" each time there is a > source code change, or even better, a change to the Gemfile. Should I modify > my preinitializer.rb ? > I tried the following, but I still need to periodically log into the > machine, cd into .cruise/projects/NAME/work and run bundle install. > Any thoughts? > > Modifying cruise.rake like this should help..... maybe we can add this to > the documentation? > > require 'rubygems' > require 'rake' > require 'fileutils' > require "bundler" > > desc "Task for cruise Control" > task :cruise do > RAILS_ENV = ENV['RAILS_ENV'] = 'test' > > sh "bundle install" > Bundler.setup(:default, :test)
I'm not sure if this is a problem with bundler or not, but we run 'bundle install' in a separate parallel interpreter session kicked off before the tests run (in their own process). Historically (e.g. with config.gems or geminstaller) , this was necessary to ensure that the RubyGems cache was not out of date and missing newly-installed gems. Bundler may not have that problem, though. Can anyone prove or disprove that you need to run 'bundle install' in a separate process from your tests? -- Chad _______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
