Configuring Build Triggers

Added by Christopher Hamilton, last edited by Pavel Sher on Dec 30, 2008  (view change)
Search
Searching TeamCity 4.x Documentation
Table of Contents

This section covers configuring all types of the build triggers in TeamCity:

VCS Triggers

With configured VCS Build Triggers TeamCity periodically polls VCS roots of the build configuration for changes, automatically detects that changes were committed and starts a new build. The poll period is defined by the root's Changes Checking Interval.

For VCS Triggers you can specify Quiet mode settings (quiet mode is a period that should pass before a build is placed into the Build Queue) and particular triggers rules. Refer to the Configuring VCS Triggers page for detailed description.

Using Quiet mode setting it is possible that at the moment the build starts to run it becomes a History Build.

Scheduled Triggers

Scheduled trigger allows to set time when a build of the configuration will be run daily or weekly. Besides you can specify more complex time settings using cron expressions (refer to the Cron Expression Build Trigger page for details).

Dependencies Triggers

Dependency triggers allow to start the build every time the build it depends on finishes successfully.

Please note, that you can also use dependencies (snapshot or artifacts) to trigger your builds automatically.

Other Triggers

These settings allow to start a build automatically if the previous build failed.
Enter a period of time in seconds to wait before the next build will be started.

Configuring Build Triggers Using Scripts

Beside above mentioned trigger settings, you can also use HTTP-GET requests to trigger your build from a script.


See Also:

Labels