abstractplain

Custom cruisecontrol.rb task to handle migrations with seed data. (for when standard cruise build task yields FK constraint violations when the fixtures start loading).

#This builds from migrations each time (slower, but more reliable).  
#Must then empty seed data before tests start to delete stuff, or FK constraints get violated.  

task :cruise do
  ENV['RAILS_ENV'] = 'test'
  puts "custom cruise task invoked.  env is hardcoded to test"

  Rake::Task["environment"].invoke
  #start from scratch with just the test db
  Rake::Task["db:test:purge"].invoke
  #necessary to reconnect, as purge drops database (and w mysql the conn)
  CruiseControl::reconnect

  #run all migrations from scratch.  slow but clean
  Rake::Task["db:migrate"].invoke

  #empty the db of data - migration has loaded seed data into the tables, 
  #which'll be deleted badly by test fixtures loader.

  #NOTE: db:test:purgetwo is just a quick hack to force this identical action to be called again
  #TODO: replace with the correct way to force execution of a task in rake
  Rake::Task["db:test:purgetwo"].invoke
  #necessary to reconnect, as purge drops database (and w mysql the conn)
  CruiseControl::reconnect

  #the migration has already done a schema dump
  Rake::Task["db:schema:load"].invoke

  success = Rake::Task["test"].invoke
  success
end

Embarrassingly, this currently needs ‘db:test:purgetwo’ to exist. I just copied pasted db:test:purge task. The correct way would be to look at how to ensure task execution in rake, but debugging cruisecontrol.rb exhausted all my patience and sanity.

See also What ‘rake test’ does.

This entry was posted on Thursday, November 8th, 2007 at 9:21 pm and is filed under RubyOnRails. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.