Label: clean-up

All content with label clean-up.
Related Labels: sources , clean , pin , build , history , policy , rule

Clean Checkout (TeamCity 4.x Documentation) Clean Checkout (also referred to as "Clean Sources") is an operation that ensures that the next build will get a copy of the sources fetched all over from the VCS. All the content of the Build Checkout Directory is deleted and the sources are refetched from the version control ...

Clean Sources (TeamCity 3.x Documentation) Clean Sources Cleaning sources means that the previous project sources are deleted from the build agent and new project sources are checked out, when the next build of the selected build configuration is created on the agent. Cleaning sources is recommended if problems occurred ...

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 ...

Pinned Build (TeamCity 4.x Documentation) build can be "pinned" to prevent it from being removed when a cleanup procedure is executed, as stipulated by the cleanup policy CleanUp. You can pin or unpin a build in the Overview tab Overview of the Build Configuration Home Page, or in the Overview tab of the Build ...

Pinned Build (TeamCity 3.x Documentation) Pinned Build  A build can be "pinned" to prevent it from being removed when a cleanup procedure is executed, as stipulated by the cleanup policy CleanUp Policy.  You can pin or unpin a build in the Overview tab Overview of the Build Configuration Home ...