Control when Tentacle retention policy step will be executed during deployment
Tentacle retention policy is executed once all deployments steps are completed. When the retention policy step starts running, it blocks any other step.
This behavior is by design and can't be configured.
This design can cause issues if for some reason the retention policy step encounters issues and takes a long time to complete.
As a workaround we can add a deployment step of a dummy package at the end of the deployment process. As result the tentacle retention is executed at the last step of the deployment.
I would like to have an option to control when the retention policy step is executed where the options should be:
* Let Tentacle decide
* At the end of the deployment process
Tony Thompson commented
Maybe an addition to the above would be to add the following to the option list above.
* Schedule a time