VCS Triggers

Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 4.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.
Search

Searching TeamCity 4.x Documentation

Table of Contents

Administration > <build configuration> > Build triggering > VCS Triggers

Option Description
Enable triggering when updated files are checked into VCS Check this option if you want to trigger build, when pending changes appear in project. When this option is checked, TeamCity will check VCS for changes every 60 seconds and trigger the build if changes are found. The time between checks can be configured in on the Server Configuration page (Administration > Edit Server Configuration) or in the VCS root settings or by modifying the Java system property modification.check.interval on the TeamCity Server as described in the TeamCity Startup Properties section.
Quiet period setting The period in seconds that must pass since the last detected change. If set, the build will be triggered only after the specified period passes. If a new change occurs within quiet period VCS trigger will wait quiet period again.
Note that when a build triggered by such VCS trigger starts it will not take changes occurred after the build triggering, that is, it will run with all changes that were committed by the end of the quiet period.

Build trigger rules Use this text area to enter the rules that determine what VCS activity will automatically trigger builds. See Configuring VCS Triggers for more information.
Save Click this button to preserve your changes.




See Also:

Labels:

quiet quiet Delete
vcs vcs Delete
trigger trigger Delete
rule rule Delete
admin admin Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.