Hi you can use the multi trigger. Project C should have a multisourcontrol, consisting of filesystem source controls.
when project A is build ok, write a file to c:\temp\check\projectA when project B is build ok, write a file to c:\temp\check\projectB now these 2 folders have changes, so project C will trigger this should do it with kind regards Ruben Willems On Wed, Sep 24, 2008 at 12:29 AM, Chris Funk <[EMAIL PROTECTED]> wrote: > > Is there any way to accomplish this at all? I've got a series of > projects to deploy to several slowly connected servers. I want to > have a project that monitors them all and sends out an e-mail when > they've all completed. > > Unfortunatly, the projects can vary by minutes in how long it takes to > do the copy, so the projectTriggers don't fire the multiTrigger > properly. > > The copy takes ~10 min and we have 8 servers, so I REALLY don't want > to do them serially. > > Any thoughts? > > Any other contributions out there that might provide a workaround? My > google searches didn't produce anything. > > Thanks, > --Chris > > On Sep 18, 3:31 am, Len Holgate <[EMAIL PROTECTED]> wrote: > > Unfortunately the multi-trigger doesn't do what you need when you use > > it with a project trigger because of how the project trigger works... > > The project trigger resets itself on each check rather than stayings > > set until integration is complete. This means that a multi-trigger > > with multiple project triggers is unlikely ever to end up with all of > > the triggers firing. I have some patches but i havent had a chance to > > submit them as they're part of a bigger change. > > > > On Sep 16, 4:23 pm, Daniel Hommel <[EMAIL PROTECTED]> > > wrote: > > > > > You might want to have a look at the multitrigger. I think it does what > > > you want. > > > > > > http://confluence.public.thoughtworks.org/display/CCNET/Multiple+Trigger > > > > > regards, > > > > > Daniel > > > > > Matt Chatterley writes: > > > > Here we go - another twist! > > > > > > Is there currently a way (I don't think there is?) to configure CCNET > to > > > > fire triggers in the following way: > > > > > > Three projects, A, B and C. > > > > > > C is triggered when either A or B complete a successful integration > BUT > > > > ONLY if BOTH "ancestors" are successfully built. > > > > > > E.g. > > > > > > Project A builds OK. B's last build outcome was OK. C should build. > > > > Project A builds OK. B's last build outcome was FAIL. C should NOT > build. > > > > > > Any input appreciated! > > > > > > Thanks, > > > > > > Matt- Hide quoted text - > > > > > - Show quoted text - >
