General Dynamics
United Kingdom LimitedHi All.I'm seeing something very odd with CCRB.A couple of days ago our build box died and a new hard disk was put in.To get CCRB back up and running I downloaded it from the web, un packed it and added the project as normal.Now when I run CCRB it constantly tries to build the project even though there hasn't been a new checkin.output says:build 3202 started.build 3202 done.build 3202 started.build 3202 done.build 3202 started.build 3202 done.the cruisecontrol.rb file in the project folder is the default one set by CCRB add.Any ideas what could be happening?This is on a windows XP box.
Doing a new check in to SVN didn't help.
It almost looks like there's parallel builds going on.
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
Work
builder.lock
builder_status.building
builder_status.error
builder_status.sleeping
cruise_config.rb
source_control.err
I've not triggered any builds from the dash board or anything like that.
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?
Thanks.
Nick.
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
Cruisecont...@rubyforge.org
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
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: cruisecontrolr...@rubyforge.org
[mailto:cruisecontrolr...@rubyforge.org] On Behalf Of Chad
Woolley
Sent: 09 July 2010 17:30
To: cruisecont...@rubyforge.org
Subject: Re: [Cruisecontrolrb-users] Why is CCRB constantly building.