Once a build configuration is created, builds can be triggered manually by clicking the Run button or initiated automatically with the help of Triggers.
A build trigger is a rule which initiates a new build on certain events. The build is put into the build queue and is started when there are agents available to run it.
While creating/editing a build configuration, you can configure triggers using the Triggers sections of the Build Configuration Settings page by clicking Add new trigger and specifying the trigger settings. For configuration details on each trigger, refer to the corresponding sections. It is possible to disable a configured build trigger temporarily or permanently using the option in the last column of the Triggers list.
For each build configuration the following triggers can be configured:
- VCS trigger: the build is triggered when changes are detected in the version control system roots attached to the build configuration.
- Schedule trigger: the build is triggered at a specified time.
- Finish Build trigger: the build is triggered after a build of the selected configuration is finished.
- Maven Artifact Dependency trigger: the build is triggered if there is a content modification of the specified Maven artifact which is detected by the checksum change.
- Maven Snapshot Dependency trigger: the build is triggered if there is a modification of the snapshot dependency content in the remote repository which is detected by the checksum change.
- Retry build trigger: the build is triggered if the last build failed or failed to start.
- Branch Remote Run Trigger: personal build is triggered automatically each time TeamCity detects new changes in particular branches of the VCS roots of the build configuration. Supports Git and Mercurial.
- NuGet Dependency Trigger: starts a build if there is a NuGet package update detected in the NuGet repository.
In addition to the triggers defined for the build configuration, you can also trigger a build by an HTTP GET request, or manually by running a custom build.