title: Cruise control.NET Integration queues?
body: <p>This is a doubt regarding the material published in the
  following link
   "<a href="http://confluence.public.thoughtworks.org/display/CCNET/Integratio+Queues" rel="nofollow noreferrer">http://confluence.public.thoughtworks.org/display/CCNET/Integratio+Queues</a>"</p>
  
  <p>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.</p>
  
  <p>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."</p>
  
  <p>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.</p>
  
  <p>Can u plz suggest any solution to this problem??</p>
  
  <p>with kind regards
  Maddy</p>