you could definitely choose to do something like either project.rake_task = "db:migrate default"
or, you could also choose to add a "cruise" rake task to your project and do whatever you'd like to do there. or, you could choose to fix whatever is causing the default cruise stuff to break in the first place. Jeremy On Thu, Sep 11, 2008 at 10:54 AM, Jason Edwards <[EMAIL PROTECTED]> wrote: > Bizarre... > > I went and added a task to my Rakefile, and I'm able to reproduce the > problem, outside CC.rb (I got this from looking at the > tasks/cc_build.rake file): > > task :cruise => :environment do > Rake::Task['db:test:purge'].invoke > Rake::Task['db:migrate'].invoke > Rake::Task['test'].invoke > end > > The other suggestion from Jeremy, to set the project.rake_task to > 'default', allowed the build to pass, however, I'm sure that a > database change would cause the build to fail, since the 'default' > task doesn't run db:migrate. > > So it's not a cruisecontrol issue at all... I'll keep hacking on it, > maybe find answer... > > Thanks, > > Jason > > On Thu, Sep 11, 2008 at 10:16 AM, Chad Woolley <[EMAIL PROTECTED]> > wrote: > > On Thu, Sep 11, 2008 at 8:55 AM, Jason Edwards <[EMAIL PROTECTED]> > wrote: > >> I ran the builder for the project with the --trace flag, hoping that > >> would shed some light on the problem, but to no avail. > > > > Try running the same rake task that cruise runs, from your CI box > > command line, but not through cruise. You can do this from a clean > > checkout, or the cruise work dir for the project (but ideally these > > should be the same, because cruise's working copy should have no > > changes). The task cruise is running will be either your default > > task, or the cruise task, or something you have overridden in your > > cruise_config.rb. It is not clear what that is from the output. > > > > When you run this manually, check the return code (echo $?). If it is > > non-zero, that is your problem - find out why. If it is zero, then > > somewhere rake is exiting with a nonzero return code, and you need to > > track it down, probably with debug statements. > > > > -- Chad > > _______________________________________________ > > Cruisecontrolrb-users mailing list > > [email protected] > > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > _______________________________________________ > Cruisecontrolrb-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >
_______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
