4.Build Triggering

Administration > <project> > <build configuration> > Build triggering

This configuration section allows you to specify events — Build Trigger — that will initiate builds of the particular build configuration.

At the top of the page TeamCity displays the following information:

• Build Configuration of the build configuration

• when the state has been changed

• a name of the user who has changed the state,

• a comment made by the user for pausing/activating the build configuration

Each tab of the Build triggering settings section is described in the corresponding page:

• VCS Triggers

• Schedule Triggers

• Dependencies Triggers

• Other Triggers

tip

Besides the build triggers mentioned above, you can also trigger Run Custom Build Dialog.

warning

Since TeamCity 5.1 Build triggering UI has been changed. Instead of adding triggers in the dedicated tabs, use Add New Trigger dialog, which is invoked by clicking corresponding link. In this dialog, choose the required trigger type and proceed with options:

Trigger type	Options Description
VCS Trigger	Options for this trigger type are the same as described in VCS Triggers.
Schedule Trigger	Options for this trigger type are the same as described in Schedule Triggers.
Build Dependency Trigger	Build dependency trigger adds build to the queue after successful build of the selected configuration.
Maven Artifact Dependency Trigger	Options for this trigger type are the same as in Dependencies Triggers.
Maven Snapshot Dependency Trigger	Maven snapshot dependency trigger adds a new build to the queue when any of the snapshot dependencies is updated in the remote repository.
Retry Build Trigger	Retry build trigger adds new build to the queue if the previous build failed.

Note that if you create a build configuration from a template it inherits build triggers defined in the template, and they cannot be edited, or deleted. However, you can specify additional build triggers.