Overview
Project cleanup rules are used to define when historical build data is cleaned from the pulse™ host server. In a perfect world, the host would have enough disk space to retain all project build data forever. However, disk space is limited, and project data (particularly working directories) may consume hundreds of megabytes per build. Cleanup rules provide a flexible way of defining when data should be cleaned to preserve disk space.
Types of Project Data
For the purpose of cleanup, build data is split into multiple categories, which may be cleaned up separately (or not at all):
| Category |
Description |
| build artifacts |
All artifacts captured during the build. Does not include copies of the artifacts in the repository. |
| working copy snapshots |
Retained snapshots of build working copies. These are not captured by default, but may be very large and thus require strict cleanup. |
| repository artifacts |
Artifact files that have been published to the internal artifact repository. |
| logs |
The logs that contain output from the build process. |
Each rule can be configured to clean up any combination of the above categories. You may alternatively choose to clean up the entire build result. Note that in this case the build will be completely removed from the project's history.
Application of Cleanup Rules
Each project has a list of cleanup rules. After each build is completed, and at regular scheduled intervals, each one of these cleanup rules is applied to the project's build history in turn. Whenever a cleanup rule matches a build result, that result (or its working directory) will be immediately cleaned.
