Thanx for the repsonse Ruben. Good luck with that merge, I hope you don't get too many headaches! I know from plenty of experience how these things go in reality ;-)
Shaun On 9 Feb, 11:37, Ruben Willems <[email protected]> wrote: > Hi > > the setup sounds ok, > concerning the poll mechanism, Craig it busy with events and so, and this > could/should replace the polling mechanism. > It will not be in the 1.4.3 release, but maybe in the one after it. > > I'm still merging the security code in the trunc, and this has taken more > time than I had foreseen :-( > > with kind regards > Ruben Willems > > On Mon, Feb 9, 2009 at 12:28 PM, CinnamonDonkey < > > [email protected]> wrote: > > > Hi, > > > Based on my fancy ASCII diagram here: > > > MASTER CCNET > > MACHINE > > + > > +-------------------+-------------------+ > > | | > > CCNET CCNET > > MACHINE A MACHINE B > > > Is it OK to have two (or more) machines run Project Triggers and both > > trigger simultaneously of one master machine/project? > > > The idea is that the master machine does a QUICK build on the project > > and machines A and B both run tasks which take a long time, but can be > > done in parallel. > > > On a side note, why does the project trigger POLL, would it not be > > better to have the dependant project be signaled a status of > > interest? > > > i.e. in the dependant projects config: > > > <signalTrigger> > > <triggerOn Signal server="//ccnetmachine" > > project="incrementalBuild" status="Failed" /> > > </signalTrigger> > > > This would save on all that polling and on the possibility that the > > time between polling might miss an event of interest. > > > Regards, > > Shaun
