...
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, and Backups) | How many days to keep artifacts 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. The name was modified in 8.0.0.7. It still has the same behavior. Additionally, the next parameter was added. | 365 | ||
Retention Clean up Days of Logs and Steps | After this many days, old project execution logs and steps will be purged even though the versions, artifacts, and backups will still be keptLogs and Steps are purged regardless of keep counts. Artifacts and Backups are not purged by this. This setting deletes data regardless of the versions that keep counts are keeping. The versions can still be deployed again, but the step details will be missing. This setting is not per project version, but per workflow execution, so older executions may have no steps, but newer ones would still have them. The project will look like this afterwards:
@Since 8.0.0.7 |
...