Label: rule

All content with label rule.
Related Labels: configure , vcs , clean-up , configuration , ui , cleanup , trigger , admin , checkout , labeling , quiet , label , build , notification , root , history , policy

Build History Clean-Up Policy (TeamCity 4.x Documentation) Administration > Configure cleanup policy On this page you can enable or disable the cleanup process, set up its timing, and configure the cleanup policy CleanUp for various build configurations. The page also informs you about the next scheduled cleanup ...

Clean-Up (TeamCity 4.x Documentation) cleanup policy defines how to clean up build data (build log messages, developers' changes, artifacts, statistical data and so on). The cleanup policy contains a number of rules, which can be defined for a specific build configuration, and a default policy ...

Clean-Up Policy (TeamCity 3.x Documentation) CleanUp Policy  A policy that defines how to clean up build data (build log messages, changes, artifacts and so on). The cleanup policy contains a number of rules, which can be defined for a specific build configuration or for all configurations. In each rule ...

Configuring Build Triggers (TeamCity 4.x Documentation) section covers configuring all types of the build triggers build trigger in TeamCity: VCS Triggers VCS triggers are the most often used With configured VCS Build Triggers TeamCity periodically polls VCS roots of the build configuration for changes, automatically ...

Configuring Build Triggers (TeamCity 3.x Documentation) Configuring VCS Build Triggers Rules VCS Build Triggers automatically start a new build each time TeamCity detects that updates have been checked into the Version Control System. By default, when this option is enabled, TeamCity scans all ...

Configuring VCS Settings (TeamCity 4.x Documentation) TeamCity, setting up VCS parameters is one of the mandatory steps of creating a build configuration. This section provides information on the following VCS Settings: Configuring VCS Roots the main part of VCS parameters set up; a VCS Root is a description of a version ...

Configuring VCS Settings (TeamCity 3.x Documentation) Configuring VCS Settings This section provides notes on configuring the following VCS Settings: Configuring VCS Roots A VCS Root is a description (a number of connection settings) of a version control system where project sources are located. VCS roots are configured on the Version ...

VCS Checkout Rules (TeamCity 4.x Documentation) VCS Checkout Rules allow you to exclude paths and/or map paths (copy directories and all their contents) to a different location on the Build Agent during checkout. To add a checkout rule click the edit checkout rules link on the build configuration's Version ...

VCS Triggers (TeamCity 4.x Documentation) 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 ...

VCS Triggers (TeamCity 3.x Documentation) VCS Triggers &nbsp;Administration > project> <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 ...