|
All content with label clean-up.
Related Labels:
pin, clean, history, policy, sources, rule, build
Page:
Clean Checkout
(TeamCity 7.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 ...
Other labels:
clean, sources, policy, build, history
|
Page:
Clean Checkout
(TeamCity 6.5.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 ...
Other labels:
clean, sources, policy, build, history
|
Page:
Clean Checkout
(TeamCity 6.0.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 ...
Other labels:
clean, sources, policy, build, history
|
Page:
Clean Checkout
(TeamCity 5.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 ...
Other labels:
clean, sources, policy, build, history
|
Page:
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 ...
Other labels:
clean, sources, policy, build, history
|
Page:
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 ...
Other labels:
clean, sources, policy, build, history
|
Page:
Clean-Up
(TeamCity 7.x Documentation)
TeamCity has a feature of automatic deletion of the data belonging to old builds. It is called Cleanup and can be run manually or each day by schedule (which is recommended). Cleanup settings are configured under Administration Projectrelated Settings Build History Cleanup. It is recommended ...
Other labels:
policy, rule, build, history
|
Page:
Clean-Up
(TeamCity 6.5.x Documentation)
TeamCity has a feature of automatic deletion of the data belonging to old builds. It is called Cleanup and can be run manually or each day by schedule (which is recommended). Cleanup rules for individual build configurations and defaults are configured under Administration > Build History ...
Other labels:
policy, rule, build, history
|
Page:
Clean-Up
(TeamCity 6.0.x Documentation)
CleanUp is a process that is run regularly and removes cleanup rulesmatching builds from the build configuration history. The process cleans build data stored on the server. This allows to clean disk space and remove obsolete builds from UI. A cleanup policy defines ...
Other labels:
policy, rule, build, history
|
Page:
Clean-Up
(TeamCity 5.x Documentation)
CleanUp is a process that is run regularly and removes cleanup rulesmatching builds from the build configuration history. The process cleans build data stored on the server. This allows to clean disk space and remove obsolete builds from UI. A cleanup policy defines ...
Other labels:
policy, rule, build, history
|
|
|
Label: clean-up