Retention policy issue

Legacy Uncategorised
1

We have a lifecycle configured as follows:

The default retention policy is
Releases: Keep 1 release
Files on Tentacles: Keep 1 release

In the Pre-Production phase, the retention policy is
Inherited from default lifecycle policy
Releases: Keep 1 release
Files on Tentacles: Keep 1 release

In the Production phase, the retention policy is
Releases: Keep 3 releases
Files on Tentacles: Keep 3 releases

When deploying to the Pre-Production Phase there are 3 releases kept.
When deploying to the Production Phase there are 1 release kept.

I’ve attached the log files.

ServerTasks-11952.log.txt - deployment to Pre-Production server
ServerTasks-11955.log.txt - deployment to Production server

We are running version 2.6.0.778.

Any help you can provide would be appreciated.

ServerTasks-11955.log.txt (41 KB)

ServerTasks-11952.log.txt (64 KB)

2

There are 3 releases kept when deploying to the Production Phase also.

3

The issue exists with the Pre-Production phase. It is configured to only keep 1 release but is keeping 3.

4

Just an update. I deleted and recreated the lifecycle. The lifecycle is configured the same way but now when I deploy to Pre-Production and Production there is only 1 release kept in each environment.

ServerTasks-11972.log.txt - deployment to Pre-Production server
ServerTasks-11974.log.txt - deployment to Production server

Pretty strange issue. Any help would be appreciated.

Thanks!

5

Forgot to attach the files.

ServerTasks-11972.log.txt (74 KB)

ServerTasks-11974.log.txt (48 KB)

6

Hi Mark,

Thanks for this, you’ve found a bug. We’ll fix it in the 2.6.2 release shortly.

Paul