Tentacle Retention can remove packages from a target that are required by another deployment currently awaiting intervention.

[calverp]

Team

• [X] I've assigned a team label to this issue

Severity

Not blocking

Version

2022.4 - assume it occurs in earlier versions

Latest Version

I could reproduce the problem in the latest build

What happened?

If you have two projects using the same package and deployment target. If one of the projects has a deployment currently awaiting manual intervention, the second project can delete the required package from the tentacle when the retention runs.

Reproduction

• Create one project with a manual intervention step and a deploy package step
• Create a second project with a deploy package step that uses the same package and target
• Set the relevant lifecycle to "Keep 1 Release on Tentacle"
• Deploy the first project deployment and leave the interruption waiting
• Deploy the second project with the same package version
• Create a new release and increment the package version in the second project and deploy
• Keep doing this until the package used by the first project is removed by retention
• Progress the interruption in the first project, it will then fail due to the missing package

Error and Stacktrace

No response

More Information

Links

shortcut

Workaround

Increasing the retention period for tentacle packages could mitigate this.