Early Access Program Features Tips & Tricks

Improved Builds History Clean-up Options

As soon as you have implemented continuous building and testing practice in your company, TeamCity starts accumulating the building process’ data such as developers’ code modifications, artifacts and so on. To help you get rid of redundant data and keep server disk space reasonable, we have a clean-up policy for the projects and build configurations.

A clean-up policy is in fact a set of rules which defines which data will be removed and from particular builds. It includes:

  • a number of successful builds of the particular build configuration to be kept,
  • builds’ data to be removed from history,
  • a time period the builds to be preserved in history.

You can also specify the so-called default rule which will be applied to all configurations and projects and override it with more appropriate rule in specific configurations. To keep some build away from the cleanup process you can use the pin build feature.

To set the clean-up policy, navigate to Administration and click the link:

On the page that opens, click the Add clean-up rule button and select the build configuration for which you want to apply the rule:
Then you can specify:

  • the data to be removed (available since the last TC 3.1 EAP build),
  • the types of builds the rule will be applied to.

In TeamCity 3.0 both the build and its artifacts were removed from history. Now you can choose between three new options and specify the data to be cleaned for each build configuration more precisely:

  • remove artifacts only (keep history and statistics)
  • remove build from history but keep statistics (build will still be shown on the TeamCity statistical charts but you won’t be able to browse build results)
  • remove everything

Use two other options to specify the age of the builds the rule is going to be applied to and the number of successful builds to be kept in history. If you can select both options, and the builds meeting both conditions will be cleaned.

We are sure this feature will allow you to optimize the server space usage on a long run.

Technorati tags: TeamCity, JetBrains, Java, clean-up, .NET, IntelliJ IDEA, continuous integration, build management, agile development, best practices, MS Visual Studio 2003, Eclipse

image description