The Interval Trigger is used to specify that an integration should be run periodically, after a certain amount of time. By default, an integration will only be triggered if modifications have been detected since the last integration. The trigger can also be configured to force a build even if no changes have occurred to source control. The items to watch for modifications are specified with Source Control Blocks.
Examples
Minimalist example:
Full example:
<intervalTrigger name="continuous" seconds="30" buildCondition="ForceBuild" initialIntervalSeconds="30"/>
Configuration Elements:
| Node |
Description |
Type |
Required |
Default |
| name |
The name of the trigger. This name is passed to external tools as a means to identify the trigger that requested the build. (Added in CCNet 1.1) |
string |
false |
IntervalTrigger |
| seconds |
The number of seconds after an integration cycle completes before triggering the next integration cycle. |
int |
false |
60 |
| buildCondition |
The condition that should be used to launch the integration. By default, this value is IfModificationExists, meaning that an integration will only be triggered if modifications have been detected. Set this attribute to ForceBuild in order to ensure that a build should be launched regardless of whether new modifications are detected. Use Source Control Blocks to specify what to watch for modifications. |
string |
false |
IfModificationExists |
| initialIntervalSeconds |
The number of seconds after server startup before triggering the first integration cycle. |
int |
false |
value of seconds |
 | This trigger replaces the PollingIntervalTrigger and the ForceBuildIntervalTrigger. |
| The initialIntervalSeconds is new in CruiseControl.Net release 1.4 |
