Purge policy

Purging outdated data injected by CI pipelines results in better performance, while retaining essential data. Each pipeline's runs are purged after a specific number of days or runs.

Overview

Purging is performed automatically to improve performance.

You can set a purging policy that retains either a set number of pipeline runs, or all pipeline runs in a set number of days.

The purging policy applies to all space pipelines. You can also set a specific policy for a particular pipeline.

Purging affects the following historical pipeline data:

Pipeline runs
Automated test runs coming from pipeline runs
Builds

Set up a run purge policy

The space admin can set the default purge policy for the space using the parameters in the table below.

At the space level, as an alternative to the parameters list, you can set the purge policy in a form. In the space, select More Settings > Purging.

Purge policy parameters

Parameter	Description
PR_PURGE_STRATEGY_TYPE	The purging strategy: days_to_keep or runs_to_keep.
PR_PURGE_NUM_DAYS_TO_KEEP	For the days_to_keep strategy type, the number of days to keep the runs.
PR_PURGE_NUM_RUNS_TO_KEEP	For the runs_to_keep strategy type, the number of runs to keep from each pipeline.

For details on setting configuration parameters, see Configuration parameters.

Note: You can override the space's global purge policy for a specific pipeline. For details, see Create and configure pipelines.

Run a manual purge

To clean up pipeline runs, you can trigger a manual purge.

To run a manual purge:

Open the Settings menu , click Spaces, and select a space.
Select More Settings > Purging.
Click Purge. You can continue working while the purge is processed.