TeamCity On-Premises
 
Get TeamCity On-Premises

Configuring VCS Triggers

Edit pageLast modified: 24 September 2024

VCS triggers automatically start a new build each time TeamCity detects new changes in the configured VCS roots and displays the change in the pending changes. Multiple VCS triggers can be added to a build configuration.

A new VCS trigger with the default settings triggers a build once there are pending changes in the build configuration: the version control is polled for changes according to the checking for changes interval of a VCS root honoring a VCS commit hook if configured. Only the changes matched by the checkout rules are displayed as pending and thus are processed by the trigger. If several check-ins are made within short time frame and discovered by TeamCity together, only one build will be triggered.

After the last change is detected, a quiet period can be configured to wait for some time without changes before the build is queued.

The global default value for both options is 60 seconds and can be configured for the server on the Administration | Global Settings page.