Null Source Control Block¶
Use the Null Source Control if you don't want to check a Source Control repository for changes. In this instance you would always want to either use a 'Force Build' Trigger or always manually start builds, from the Web Dashboard or CCTray.
Version¶
Available from version 1.0
Examples¶
1<sourcecontrol type="nullSourceControl" />Configuration Elements¶
| Element | Description | Type | Required | Default | Version |
| type | The type of source control block. | String - must be nullSourceControl | Yes | n/a | 1.0 |
| alwaysModified | Defines wheter or not to always indicate that there were modifications | Boolean | No | false | 1.7 |
| changeNumberType | What kind of type is the changenumber (revision number) of the sourcecontrol Possible values : guid, integer, empty | String | No | empty | 1.7 |
| failGetModifications | Defines wheter or not to fail the checking for modifications. | Boolean | No | false | 1.5 |
| failGetSource | Defines wheter or not to fail the getting of the source. | Boolean | No | false | 1.5 |
| failLabelSourceControl | Defines wheter or not to fail the labeling. | Boolean | No | false | 1.5 |
Notes¶
Strictly speaking, this element isn't required. The build server will behave the same way if there are no Source Control Blocks. Still, it's useful to include this in configuration files to make it clear. This source control is mostly used for simulating or test purposes.
Automatically Generated¶
Documentation generated on Monday, 26 May 2014 at 7:18:02 AM