so if you request a build through the ui, it should start the builder. also, all builders should automatically start when you run "./cruise start". if the builder doesn't start, check the builder log for it.
one situation that results in this is when you add a project after cruise is already started. this is normal, and as stated above, the suggested way to start the builder is through the dashboard's request build. Jeremy On Jan 30, 2008 5:48 PM, Chad Woolley <[EMAIL PROTECTED]> wrote: > On Jan 30, 2008 6:04 PM, Will Sargent <[EMAIL PROTECTED]> wrote: > > I can't find any documentation that would tell me about this. Any log > > files I should provide? > > > > Will. > > The builder process (not the ccrb rails app process) is not running. > Each project has a separate, dedicated, builder process. > _______________________________________________ > 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
