Hi
than this is a bug :-( Made a bug report : http://jira.public.thoughtworks.org/browse/CCNET-1449 let's see what we can do to solve it with kind regards Ruben Willems On Mon, Apr 6, 2009 at 8:44 AM, madhu nambiar <[email protected]>wrote: > Hi, > Cruise Control.NET 1.4.3. > > > with regards > Maddy > > On Mon, Apr 6, 2009 at 12:04 PM, Ruben Willems <[email protected]>wrote: > >> Hi >> >> which version of CCNet are you using ? >> >> with kind regards >> Ruben Willems >> >> >> >> >> On Mon, Apr 6, 2009 at 7:31 AM, Maddy <[email protected]> wrote: >> >>> >>> Hi , >>> This is a doubt regarding the material published in the >>> following link >>> "http://confluence.public.thoughtworks.org/display/CCNET/Integration >>> +Queues" >>> >>> >>> which tells that "The default behaviour of CruiseControl.Net is that >>> each project defined in the configuration is given its own integration >>> thread, thereby allowing differently named projects to build >>> concurrently. >>> >>> Note however that a single project can never be building more than >>> once at the same time. If you force a build on Project X while it is >>> already integrating, that force build request is effectively blocked >>> until the previous integration completes. So you can also think of >>> this as each project having its own dedicated integration queue, where >>> only the item at the head of the queue can be currently building, with >>> at most one request pending." >>> >>> But this is really contradicting in my case as when i force my build >>> it opens my IDE and starts the integration and building which takes >>> about 3 min approx. but when i force my build in between the execution >>> on my webdash board i see that it again opens another IDE and starts >>> the building which is not acceptable.According to the link shown >>> above,it should queue and wait for the 1st IDE execution to complete >>> and then go for the 2nd one. >>> >>> >>> Can u plz suggest any solution to this problem?? >>> >>> with kind regards >>> Maddy >>> >> >> >
