...
- 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 (e.g. ifRetention Days is1 day, anything which was deployed more than 1 day ago AND is one that needs to be kept to satisfy theKEEPparameters will be retained). - 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 you would need to perform a new build using the same revision of the source code.
- 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.
Examples of configuring the purge
Scenario 1: Retain the last 3 successful builds in each environment/instance and keep the last 12 successful builds and last 2 failed builds overall. Artifacts will be purged from the file system after 15 days and execution data will be archived after 30 days. Data will remain in the archive for 365 days.
...
| title | Click to show properties |
|---|
...
Scenario 2: Retain 60 days of execution data and artifacts
...
| title | Click to show properties |
|---|
...
Understanding the purge KEEP parameters
...
| width | 15% |
|---|
Project Deployments:
...
PROD
...
Properties:
...
- 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 you would need to perform a new build using the same revision of the source code.