The Purge Settings define the configuration parameters to manage the purging of FlexDeploy execution data from the database repository, and purging of the artifacts stored in the artifacts repository. These settings should be carefully adjusted to meet your data retention requirements for audit, and at the same time purging data which is no longer required to ensure a high performing system.
Property | Description | ||
---|---|---|---|
Purge Enabled | Indicates whether the purge process is enabled. Purge runs every 24 hours if enable, beginning with a few minutes after server startup. If you have concerns with running purge at some specific milestone deployment event, you can disable the purge temporarily. | ||
Keep Success Count | How many successful project version builds to keep regardless of Retention Days (Operational)
| ||
Keep Failed Count | How many failed project version builds to keep regardless of Retention Days (Operational)
| ||
Keep Count | How many project versions to keep for each environment/instance regardless of Retention Days (Operational). This helps you keep a specific number of latest deployments so that you can revert back to previous versions if desired. | ||
Keep Pipeline Executions by Release Count | How many pipeline executions to keep per release. | ||
Retention Days | How many days of execution data to keep.
| ||
Retention Days (Artifacts and Logs) | How many days to keep artifacts and execution logs. |
...