In that case, there's no way to currently prevent the second project from starting. CC.NET uses a fire and forget mechanism in the publisher. It is something we are looking into for a future release (as it will have an impact on distributed builds), but for the current version (and 1.5) I don't think it is possible.
Craig ________________________________ From: Jeff <[email protected]> To: ccnet-user <[email protected]> Sent: Mon, October 19, 2009 1:08:34 AM Subject: [ccnet-user] Re: How to get project-triggered project to wait until publishing finished? Yes, and that works, but I'd prefer to keep project B in a different queue, so that it can run in parallel with other projects. Thanks, Jeff On Oct 18, 2:00 am, "Craig & Sammi Sutherland" <[email protected]> wrote: > Have you tried putting them both in the same queue? A queue only allows one > project to run at a time, so project B won't be able to start until project > A has finished. > > Documentation on queues is > athttp://confluence.public.thoughtworks.org/display/CCNET/Integration+Q.... > > Craig > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > > Behalf Of Jeff > Sent: Saturday, 17 October 2009 7:48 a.m. > To: ccnet-user > Subject: [ccnet-user] How to get project-triggered project to wait until > publishing finished? > > Hi - > > I have a pair of projects, A and B. B is set to be triggered by the > successful completion of A. This is happening -- but too soon. It > looks like execution of B is not waiting for A's publisher to finish, > and so B doesn't have a "full loaf" to work with when it starts up. > > How can I get project B to wait until A's output has been published? > Do I have to switch from using a publisher for the output, and instead > use some sort of copy task? > > Thanks for the guidance. > > Jeff
