I can think of 2 methods. 1) (Requires version 1.5) All the builds that you want blocked should have their name prefixed by a value (eg EXE_), then use a CruiseServer Action to 'Stop' the projects starting with that name (<project>EXE_*</ project>). http://confluence.public.thoughtworks.org/display/CCNET/CruiseServer+Control+Action
2) Add a 'category' to every project that you want blocked (eg EXE), then use a script which will go through every project and if its category contains that stop it. A script that does that can be found here: http://rubenwillems.blogspot.com/2009/05/ccnet-how-to-upgrade-to-new-version.html PS And once your build is done do the reverse to start it up again. Arieh On Sep 16, 11:53 pm, hhowe29 <[email protected]> wrote: > > Is the goal (essentially) to be able to define two queues, e.g: > > > Queue1: DLL > > Queue2: EXE > > > With the logic that N projects in the SAME QUEUE as each other could build > > in parallel, but the queues would LOCK EACH-OTHER. > > > So: > > > DLL_1 and DLL_2 could build at the same time > > > DLL_1 and EXE_1 could not build at the same time (locking) > > That is close. I don't want DLL_1 and DLL_2 to build at the same time. > DLL_2 might depend on DLL_1. For the DLLs, cc.net pretty much already > gives me what I need. > > Otherwise you are correct. I don't want EXE_1, EXE_2 ... EXE_N to > build a the same time as any DLL. But if the DLL queue is empty, I > should be able to build all of the EXEs at the same time. > > > What would feelings be on tackling this as a "queueBuildType" or similar - > > e.g Parallel, Single.. etc? > > That would do. A purist might argue that a parallel queue is no queue > at all. Fortunately, I'm not a purist. > > For now, I am living with the EXE's building in sequence. They build > pretty fast, and I would rather sacrifice a little performance in > order to have a clean ccnet.config file to maintain. > > H^2
