The Purge Settings define the configuration parameters to manage the archiving and 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 day if enabled. Run time is dependent on when FlexDeploy was started24 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 Purge 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) (Note: this
| |||
| 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 out to previous versions if desired. | |||
| Keep Pipeline Executions by Release Count | How many pipeline executions to keep per release. | |||
Retention Days (Operational) | How many days of execution data to keep in the operational tables. After this data will be moved to Archive tables. .
| |||
Retention Days (Artifacts and Logs) | How many days to keep artifacts and execution logs . | |||
Retention Days (Archive) | How many days of execution data to keep in the archive tables. Age of data is determined based on original created time. This means that you should keep this value higher than Retention Days (Operational). No criteria are performed on the data which is already in the archive tables other than time. |
Purge Rules
- Any workflow execution that is the last successful deployment to an environment is automatically excluded from the purge.
- The four KEEP related parameters override the
DAYSparameters (ie.eg. ifRetention Days (Operational)isis1 day, anything that which was deployed more than 1 day ago AND is one that needs to be kept to satisfy theKEEPparameters will be excluded from the archive/purge).There is no archive of artifacts or plugin logsretained). - When artifacts have been purged, a red circle will appear on the project version indicating that the artifacts have been purged. This project version will also no longer be available to deploy to any environment. To redeploy this version , the version you would need to perform a new build using the same revision of the source would need to be retrieved from source code repository (like SVN) in use and taken through the build/deploy cycle again.
- The
Retention Daysare based on the first date it finds 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.
Examples of configuring the purge
...