This will work. I was looking for a solution that would be less maintenance in the ccnet.config if I changed the acceptance test projects. To use this method I would have to remove the triggers from the acceptance tests and add each project as a force build step for Build project. Which could become a pain if I add/remove projects for testing.
However, currently this appears to be the best solution. Thanks On Dec 17, 6:15 pm, Ruben Willems <[email protected]> wrote: > Hi > > Maybe this can help > :http://confluence.public.thoughtworks.org/display/CCNET/ForceBuildPub... > > with kind regards > Ruben Willems > > On Fri, Dec 17, 2010 at 2:59 PM, NickCollier > <[email protected]>wrote: > > > > > > > > > CrusieControl.NET setup. > > > Project: Build > > - monitors source control and will build my application. > > > Project: TestXP1 > > Queue="xp" > > - run test automation on a remote XP machine to validate the build. > > Project: TestXP2 > > Queue="xp" > > - run test automation on a remote XP machine to validate the build. > > > Project: TestVista1 > > Queue="vista" > > - will run test automation on a remote Vista machine to validate the > > build. > > Project: TestVista2 > > Queue="vista" > > - will run test automation on a remote Vista machine to validate the > > build. > > > (This is simplified, I have many more OS's that are required to > > validate a build) > > > I am having an issue that a new build may be triggered before the test > > verification of that last of have succeeded. > > I am looking for a solution to stop the Build project to running until > > all other projects having finished building (regardless of their > > status) > > > Thanks
