Actually I think this will still cause the same issues. As ForceBuild runs asynchronously.
E.g. Update to source control, Build Project runs and Forces the projects XP1 and XP2 XP1 will run and XP2 will be in the queue. While XP1 is running another update could happen on source control. The Build Project will run again and immediately update the build output folder. The XP2 Project still in the queue from the first source control update will now use the updated build output and it will never test the output from the first update. I need a way to block the Build Project from running until all the projects it forces or are triggered by it have completed. Thanks. On Dec 19, 12:51 pm, NickCollier <[email protected]> wrote: > 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
