Re: new here, status of distributed?

On 04/19/12 at 06:55pm, Bram de Jong wrote:
> Hi All,
> 
> 
> I'm new to this list, and to CC in general!
> 
> We're a small belgium based company that specialize in audio software
> and we got directed to CC by a long time user...
> 
> I was wondering how the distributed part of CC is getting along: all
> our stuff runs on linux, osx and windows, so we really could use it! I
> think we even really need it - I don't want to be looking at 3
> different status pages all the time.
> 
> 
> That said, CC does look a lot less intimidating than some other things
> out there -coughJenkinscough- and less intimidating is what I love!
> 
> grts,
> 
> 
>  - bram

For distributed builds, what you're probably looking for is the
dashboardurl switch:

./cruisecontrol.sh -dashboardurl http://maindash:8080/dashboard

Also, for distributed, you'll need to have the cruisecontrol/logs and
cruisecontrol/artifacts directories shared out to the builders somehow
(I use NFS, works great) and the main dashboard server needs to be able
to resolve the names of the machines running the other instances of
cruise control, in order to force runs of builds.

Pretty simple and works great.

Tim

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2