That's what I understood too. But to me the term "queue" implies a sequential process of the items in the queue. If it's parallel, then it no longer is a queue but rather a group or a similar concept (bag?)
On 16 sep, 11:04, Matt Chatterley <[email protected]> wrote: > Just trying to clarify (got a bit confused - early morning and not enough > coffee)! > > 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) > > If thats right, then you're right, it's almost a case of (under the hood) > wanting each DLL project and each EXE project to be in it's own queue, all > set to lock the other type - a pain to set up by hand, but just about > do-able. > > What would feelings be on tackling this as a "queueBuildType" or similar - > e.g Parallel, Single.. etc? > > -- > Matt Chatterley > Mattched IT Ltd > > http://www.mattchedit.com > Tel: 02392 987 801 > Skype: mattchedit > > UK Registered Company: 05861949 > > On 16 September 2010 09:57, OBones <[email protected]> wrote: > > > Hum sorry, yes, you are already using it. > > What you want is to avoid having to manually add them to the lockQueue > > list... > > > On 16 sep, 10:56, OBones <[email protected]> wrote: > > > I believe what you want is already available: > > > >http://confluence.public.thoughtworks.org/display/CCNET/Queue+Configu... > > > > It is indicated that this is available from version 1.4.2
