This page last changed on Dec 02, 2009 by csut017.
The Schedule Trigger is used to specify that an integration should be run at a certain time on certain days. By default, an integration will only be triggered if modifications have been detected since the last integration. The trigger can be configured to force a build even if have occurred to source control. The items to watch for modifications are specified with Source Control Blocks.
Available from version 1.0
<scheduleTrigger time="23:30" buildCondition="ForceBuild" name="Scheduled">
|| 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.
|| String - one of:
|| The name of the trigger. This name is passed to external tools as a means to identify the trigger that requested the build.
|| Adds a random amount of minutes between 0 and set value to the time. This is mainly meant for spreading the load of actions to a central server. Value must be between 0 and 59.
|| The time of day that the build should run at. The time should be specified in a locale-specific format (ie. H:mm am/pm is acceptable for US locales.)
|| The week days on which the build should be run (eg. Monday, Tuesday). By default, all days of the week are set.
|| String array
The following values are valid:
Use the buildCondition property if you want to run a scheduled forced build.
this class replaces the PollingScheduleTrigger and the ForceBuildScheduleTrigger.
Documentation generated on Tuesday, 1 Dec 2009 at 11:54:58 PM