Issue:
When a deployment step has it's name changed any previous deployments are no longer cleaned up as part of the deployment retention policy.
Testing:
Create a lifecycle set to keep 5 releases on a Tentacle
Create a project with that lifecycle
Add a deployment step (Step-Deploy for this example)
Perform 5 releases
Confirm that all releases are still being kept by the retention policy tasks
Rename Step-Deploy to Step-Deploy - Testing Application
Perform 3 releases
You will see that the retention policy task is only reporting on those 3 releases, the first 5 releases are not shown - Did not find any deployments to clean up
At this point if you check the DeploymentJournal for that machine you will see 8 releases for that project, the first 5 for Step-Deploy and the 3 for Step-Deploy - Testing Application
If you keep going with releases for Step-Deploy - Testing Application they will get cleaned up when you exceed the specified number of releases in the retention policy.
Resolution
One possible resolution would be to use the Step ID in the DeploymentJournal rather than the step name as this won't change over time (unless the step is deleted and re-created)
droyad
commented
6 years ago
Issue: When a deployment step has it's name changed any previous deployments are no longer cleaned up as part of the deployment retention policy.
Testing: Create a lifecycle set to keep 5 releases on a Tentacle Create a project with that lifecycle Add a deployment step (
Step-Deployfor this example) Perform 5 releases Confirm that all releases are still being kept by the retention policy tasks RenameStep-DeploytoStep-Deploy - Testing ApplicationPerform 3 releases You will see that the retention policy task is only reporting on those 3 releases, the first 5 releases are not shown -Did not find any deployments to clean upAt this point if you check the DeploymentJournal for that machine you will see 8 releases for that project, the first 5 for
Step-Deployand the 3 forStep-Deploy - Testing ApplicationIf you keep going with releases for
Step-Deploy - Testing Applicationthey will get cleaned up when you exceed the specified number of releases in the retention policy.Resolution One possible resolution would be to use the Step ID in the DeploymentJournal rather than the step name as this won't change over time (unless the step is deleted and re-created)