The Purge Settings define the configuration parameters to manage the purging of FlexDeploy execution data from the database repository, purging of the artifacts stored in the artifacts repository, and purging of backups. 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 | Default Value | ||
|---|---|---|---|---|
Purge Enabled | Indicates whether the purge process is enabled. Purge runs every 24 hours if enabled, 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. | false | ||
Keep Success Count | How many successful project version builds to keep regardless of Retention Days
| 2 | ||
Keep Failed Count | How many failed project version builds to keep regardless of Retention Days
| 1 | ||
Keep Count | How many project versions to keep for each project/target regardless of Retention Days. This helps you keep a specific number of latest deployments so that you can revert back to previous versions if desired. | 2 | ||
Keep Pipeline Executions Count | How many pipeline executions to keep per release. | 200 | ||
Retention Days | How many days of execution data to keep. If you would like to retain one year worth of history for deployments, keep this value to 365 or higher and control space usage by using lower value for Retention Days (Artifacts and Logs). We recommend using Keep Success Count along with Retention Days to make sure specific number of successfully deployed versions are retained irrespective of Retention Days parameter.
| 730 | ||
Retention Days (Artifacts, Logs, and Backups) | How many days to keep artifacts, execution logs, and backups. Artifacts and Logs are always kept for executions that are not purged due to Keep criteria, hence latest versions will always have artifacts and logs. | 365 |
Purge Rules
Any workflow execution that is the last successful deployment to an environment is automatically excluded from the purge, unless the project, environment, or target group is inactive.
The four
KEEPrelated parameters override theDAYSparameters (e.g. if Retention Days is 1 day, anything which was deployed more than 1 day ago is still retained if necessary to satisfy the KEEP parameters).For project version
KEEPrelated parameters, the sum ofKeep Success CountandKeep Failed Countwill take priority over theKeep Countif it is higher and visa versa. For example, lets say the system was configured with aKeep Success Countof 1,Keep Failed Countof 2, and aKeep Countof 2. If a project only had 2 successful project versions, then both project versions would be kept as theKeep Countwould take priority. On the other hand, if a project had 3 successful and 5 failed project versions, then only 1 successful and 2 failed project versions would be kept to satisfy theKeep Success CountandKeep Failed Count.The
Retention Daysare based on the first date found in this sequence:End time of the workflow execution
Start time of the workflow execution
Created time of the workflow execution
Requested start time of the workflow request
Created time of the workflow request.
Purged executions will not show up on any reports.
When artifacts have been purged, a red triangle will appear next to the project version indicating that the artifacts have been purged. These project version can no longer be deploy to any environment. To redeploy you would need to perform a new build using the same revision of the source code.
