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
