Queue Configuration Element¶
Configure the behaviour of the build queues.
Version¶
Available from version 1.4.2
Examples¶
Full Example
1<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 * ApplyForceBuildsReAddTop * 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 |
| projects | The list of projects for the queue. | List`1 | No | none | 142 |
Notes¶
Duplicate Handling¶
There are 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.
1<cruisecontrol>
2 <queue name="Q1" duplicates="UseFirst" />
3 <project name="MyFirstProject" queue="Q1" queuePriority="1">
4 <otherProjectSettings />
5 </project>
6</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.
1<cruisecontrol>
2 <queue name="Q1" duplicates="ApplyForceBuildsReplace" />
3 <project name="MyFirstProject" queue="Q1" queuePriority="1">
4 <otherProjectSettings />
5 </project>
6</cruisecontrol>The following example shows how to configure a queue so that force build requests will remove existing non forced requests of the interval trigger and re-add the force build request. This is changing the position of the request in the queue. Basically : remove the interval (non forced) builds and add the forced builds via the queue priority setting
1<cruisecontrol>
2 <queue name="Q1" duplicates="ApplyForceBuildsReAdd" />
3 <project name="MyFirstProject" queue="Q1" queuePriority="1">
4 <otherProjectSettings />
5 </project>
6</cruisecontrol>The following example shows how to configure a queue so that force build requests will remove existing non forced requests of the interval trigger and re-add a force build request to the first item in the queue.
1<cruisecontrol>
2 <queue name="Q1" duplicates="ApplyForceBuildsReAddTop" />
3 <project name="MyFirstProject" queue="Q1" queuePriority="1">
4 <otherProjectSettings />
5 </project>
6</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.
1<cruisecontrol>
2 <queue name="Q1" lockqueues="Q2" />
3 <queue name="Q2" lockqueues="Q1" />
4 <project name="MyFirstProject" queue="Q1" queuePriority="1">
5 <otherProjectSettings />
6 </project>
7 <project name="MySecondProject" queue="Q2" queuePriority="1">
8 <otherProjectSettings />
9 </project>
10</cruisecontrol>Automatically Generated¶
Documentation generated on Monday, 26 May 2014 at 7:18:00 AM