>From the content of the blog it seems like most of that is related to a CC 2.0 branch that Craig was working on that I guess was abandoned? He hasn't posted in over a year there and I don't see any checkins from him anymore in the depot. Sad since looking over most of his posts related to 'vNext' describes the CCNet I wish I had.
On Tuesday, September 18, 2012 11:24:21 PM UTC-7, Ruben Willems wrote: > > Hi > > you can find more about it here : > http://csut017.wordpress.com/tag/distributed-version/ > > I've never used it, so I can offer no extra help. > > > > with kind regards > Ruben Willems > > On 19 September 2012 01:58, Jason Fisher <[email protected]<javascript:> > > wrote: > >> I'm relatively new to CC.net and trying to set up our CI here. I've >> stumbled upon the remoteTargets project config setting found >> here<http://www.cruisecontrolnet.org/projects/ccnet/wiki/Project_Configuration_Block> >> and >> am curious how it's used since I can't find any information on it. What >> I'm hoping it does is allow multiple CC machines to process the job from a >> common queue. I'm trying to set up the following: >> >> When a changelist is submitted to perforce a 'master project' kicks off, >> it basically only exists to ForceBuildPublish about a dozen other projects >> which are all compiling our source for various platforms/configs. Because >> each individual project is capable of taxing the system it runs on I don't >> want them to all run at the same time so they all share a common queue. >> Right now they all run on the one test machine I've been experimenting >> with CC on but I would like to have 3 or 4 machines able to process this >> queue, will remoteTargets allow this? Does the remote machine have to have >> the exact same config file? >> >> Thanks, >> Jason >> > >
