Hi Chad. The builds for each project are happening one at a time but as soon as one finishes the next one for the same revision number starts.
I'll switch off the parallel builds option but my understanding of this is that this is mostly aimed at builds for multiple projects. As you say, it probably looks like a case of getting debugging. Thanks. Nick. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Chad Woolley Sent: 09 July 2010 17:30 To: [email protected] Subject: Re: [Cruisecontrolrb-users] Why is CCRB constantly building. On Fri, Jul 9, 2010 at 5:22 AM, <[email protected]> wrote: > Doing a new check in to SVN didn't help. > It almost looks like there's parallel builds going on. Turn off concurrent/parallel builds in the cruise site config. > The content of the project folder in cruise data is quite interesting. > It looks like this: > > build-3213 > build-3213-failed.in0s > build-3213-failed.in1s > build-3213-failed.in2s > build-3213-failed.in3s > build-3213-failed.in4s > build-3213-failed.in5s > build-3213-failed.in7s > build-3213-failed.in8s > build-3213-failed.in9s > build-3213-failed.in10s > build-3213-failed.in12s > build-3213-failed.in55s > build-3214 > build-3214-failed.in1s > build-3214-failed.in2sbuild-3214-failed.in3s > build-3214-failed.in4s > build-3214-failed.in7s > build-3214-failed.in8s > build-3214-failed.in10s What are the timestamps? Are these happening right after another? > I don't really want to try it on another machine as in the end it has to > run on this build box. > Any more ideas? Debug ccrb code and see what is happening. _______________________________________________ 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
