> 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
