Queues in CruiseControl.NET

Queues can be defined in one of two ways:

Implicitly: When a queue is defined in a project element, a queue will be automatically created. This will have the default settings for a queue.
Explicitly: This is when a queue element is added to the configuration. Note: projects still need to have the queue element, otherwise they will not be associated with the queue.

By default, projects belong to a queue with the same name as the project, so if no queue name is defined in the project, a queue will be implicitly defined with the same name as the project.

Queue Configuration Element

Configure the behaviour of the build queues.

Version

Available from version 1.4.2

Examples

Full Example

<queue name="Q1" duplicates="UseFirst" lockqueues="Q2,Q3" />

See the notes for additional examples.

Configuration Elements

Element	Description	Type	Required	Default	Version
duplicates	Defines how duplicates should be handled.	String - one of: UseFirst ApplyForceBuildsReAdd ApplyForceBuildsReplace	No	UseFirst	1.4.2
lockqueues	A comma sperated list of queue names that the queue should acquire a lock against.	String	No	none	1.4.2
name	The name of the queue.	String	Yes	n/a	1.4.2

Notes

Duplicate Handling

There are three different settings that can be used to specify how force build requests should be handled.
The default behaviour is to not allow force build requests to update the queue and use the first request that was added.
The following example shows how to explicitly configure the default behavior.

<cruisecontrol>
  <queue name="Q1" duplicates="UseFirst" />
  <project name="MyFirstProject" queue="Q1" queuePriority="1">
                ...
              </project>
</cruisecontrol>

The following example shows how to configure a queue so that force build requests will replace existing requests of the interval trigger without changing the position of the request in the queue.

<cruisecontrol>
  <queue name="Q1" duplicates="ApplyForceBuildsReplace" />
  <project name="MyFirstProject" queue="Q1" queuePriority="1">
                ...
              </project>
</cruisecontrol>

The following example shows how to configure a queue so that force build requests will remove existing requests of the interval trigger and re-add a force build request. This is changing the position of the request in the queue.

<cruisecontrol>
  <queue name="Q1" duplicates="ApplyForceBuildsReAdd" />
  <project name="MyFirstProject" queue="Q1" queuePriority="1">
                ...
              </project>
</cruisecontrol>

Locking

The following example shows how to configure two queues, Q1 and Q2, that acquire a lock against each other. That means that while the queue Q1 is building a project the queue Q2 is locked. While Q2 is building Q1 is locked. To specify more than one queue that should be locked use commas to separate the queue names within the lockqueues attribute. Of course the lockqueues attribute can be used together with the duplicates attribute explained above.

<cruisecontrol>
  <queue name="Q1" lockqueues="Q2" />
  <queue name="Q2" lockqueues="Q1" />
  <project name="MyFirstProject" queue="Q1" queuePriority="1">
                ...
              </project>
  <project name="MySecondProject" queue="Q2" queuePriority="1">
                ...
              </project>
</cruisecontrol>

Automatically Generated

Documentation generated on Wednesday, 25 Nov 2009 at 4:41:55 AM

Document generated by Confluence on Jan 30, 2010 19:06