Re: How to enable multiple cruise control servers co-work?

Hi Leigh,
Thanks for your infomation. I try to do as the document says. But the
document just give very high level message. Do you any more detail document.
Below is the steps I try to do. Would you please take a look?
1. Download the source code and enter ..\cruisecontrol\contrib\
2. Run ant to build the plugin.
3. Download the binary version.
4. Change the config.xml. adding
   <plugin name="distributed"
classname="net.sourceforge.cruisecontrol.builders.DistributedMasterBuilder"/>.


But i don't know how to connect the distributed to the installed verion of
the CC.

Thanks in advance.
Allen

2010/1/8 Leigh Moulder <[email protected]>

>  Hi Allen,
> I think there are a couple of ways you could tackle this.
>
> I was able to setup a similar build environment where I had one 'master'
> build server that was controlling multiple other build servers.  In my case,
> the master was a Windows machine, while the other build servers were various
> flavors of Linux.  I  was able to configure everything using the
> 'distributed' extensions found in the contrib directory.  Instructions can
> be found at:
> http://cruisecontrol.svn.sourceforge.net/viewvc/cruisecontrol/trunk/cruisecontrol/documentation/distributed/index.html
> .
>
> The nice thing with this route was that I could actually control all the
> builds from the master build server, and I knew exactly what each one was
> doing.  I was also able to setup some tricky build scenarios where one of
> the Linux builds (the one that took the longest) would only build if the
> Windows build was successful.  The downside was that it took me a couple of
> days to get everything working and configured the way I wanted.
>
> But if you wanted something faster, and that only provided status reports,
> then you should be able to use the ftppublisher or scp publisher.  I think
> you'll just need to copy the files from your client machines to your master
> machine's log directory, being sure to create a new sub-directory for each
> of these client projects.
>
> Leigh
>
>
>
> on 1/7/2010 1:19 AM Richard wrote:
>
> Our product support 4 UNIX platforms and windows. Each one has its cruise
> control to do build control. As there exist 5 servers, I need go to each one
> and check the build status or build error issue.
>
> 1. *Can I use one of them as central server (A) and others as client (B,
> C, D, and E)?* The client send build result to the central server? So I
> can get the build status of all the platforms?
>
> 2. Is there any internal communication protocol or tools to enable this
> feature? And How to config it?
> 3. One way I know is to use ftp publisher, each client send build result to
> the server, write another program on the server machine to get the overall
> status of all platforms. But it is not very straightforward. Any idea is
> welcome. Thanks.
>
> Allen
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customershttp://p.sf.net/sfu/verizon-dev2dev
>
>
> _______________________________________________
> Cruisecontrol-user mailing [email protected]://lists.sourceforge.net/lists/listinfo/cruisecontrol-user
>
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Cruisecontrol-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user
>
>

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev

_______________________________________________
Cruisecontrol-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user