|
Content with label policy in TeamCity 6.5.x Documentation (See content from all spaces)
Related Labels:
clean, configuration, agent, requirement, clean-up, run, assign, project, history, sources, rule, build
Page:
Assigning Build Configurations to Specific Build Agents
sometimes necessary to manage the Build Agents Build Agent' workload more effectively. For example, if the timeconsuming performance tests are run, the Build Agents with low hardware resources may slow down. As a result, more builds will enter the build queue ...
Other labels:
build, configuration, agent, project, run, assign, requirement
|
Page:
Clean Checkout
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, clean-up, build, history
|
Page:
Clean-Up
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:
clean-up, rule, build, history
|
Page:
Run Configuration Policy
run configuration policy allows you to select the specific build configurations you want a build agent to run. By default, build agents run all compatible build configurations and this isn't always desirable. The run configuration policy ...
Other labels:
run, configuration
|
|
|