The Multiple Trigger is used to support the execution of multiple nested triggers. Each trigger will be executed sequentially in the order specified in the configuration file. By default, if any of the triggers specify that a build should occur then a build will be triggered. The build condition will be ForceBuild if any trigger returns a ForceBuild condition. Otherwise, the build condition will be IfModificationsExist if any trigger returns that condition. Multiple Triggers can contain nested multiple triggers.
It is possible to change the logical operator applied to assessing the build conditions. If the Multiple Trigger's operator property is set to "And" then if any trigger says that a build should not happen, then the build will not happen. This is particularly useful when using multiple Filter Triggers.
Like all triggers, the multiTrigger must be enclosed within a triggers element in the appropriate Project Configuration Block.
Available from version 1.0
1<multiTrigger operator="And"> 2 <triggers> 3 <urlTrigger url="http://server/page.html" seconds="30" buildCondition="ForceBuild" /> 4 <filterTrigger startTime="23:30" endTime="23:45"> 5 <trigger type="intervalTrigger" seconds="60" /> 6 <weekDays> 7 <weekDay>Sunday</weekDay> 8 </weekDays> 9 </filterTrigger> 10 </triggers> 11</multiTrigger>
|operator||The logical operator to apply to the results of the nested triggers (And or Or).|| String - one of:
* Or * And
|triggers||The nested triggers.||Trigger Blocks array||No||n/a/||1.0|
Documentation generated on Monday, 26 May 2014 at 7:18:05 AM