Hi Nikhil Queues are more about controlling access to limited resources. For example, a server might have two projects which both modify a database. If they run at the same time, they might cause each other to fail because of the database modifications. Project A could insert a row, Project B drops the table, and then Project A looks for the row. Project A can't find it, and fails.
To solve this, you could set up a Database queue. Both project A and project B would be members of the queue. Now, if Project A and Project B are both triggered at the same time only one will run and the other will wait. This way they won't interfere with each other and may both pass. A second request for a build is ignored while a build is running. I think the assumption behind that is users will always want to wait for the results of the current build before deciding what to do next. It is only an assumption though. Dave Cameron CruiseControl.NET - http://ccnet.thoughtworks.com On Thu, Jan 22, 2009 at 8:13 PM, Nikhil <[email protected]> wrote: > > Hi There, > > I'm using 1.4.2. Could someone throw some light on the concept of > Queues in CCNET. I was under the impression that the queue would help > me in catering to multiple build requests for the same projects, which > does not seem to be the case when I started using it. > > I can not request for another build on the same project if the project > is already building. > > What is the purpose of queues then? > > Regards, > Nikhil
