Page Comparison

...

• 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 KEEP related parameters override the DAYS parameters (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 KEEP related parameters, the sum of Keep Success Count and Keep Failed Count will take priority over the Keep Count if it is higher and visa versa. For example, lets say the system was configured with a Keep Success Count of 1, Keep Failed Count of 2, and a Keep Count of 2. If a project only had 2 successful project versions, then both project versions would be kept as the Keep Count would 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 the Keep Success Count and Keep Failed Count.

• The Retention Days are 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 deployed to any environment. To redeploy you would need to perform a new build using the same revision of the source code.

...