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 -
