I’ve run into an issue using the “Deploy a Release” step and retention policies. This is the scenario:
- “Project A” has a deploy a release step to deploy “Project B”, both with release number “1.2.3”
- Project B has a different retention policy, and has release 1.2.3 deleted
- Project A now has a release that cannot be deployed, as it references a non-existent release of Project B.
I was under the impression that because the release of Project A references the release of Project B, it would be kept, just like the retention policy keeps packages referenced by releases. They currently use different retention policies as Project B is actually a shared project used by many different projects. Is this a bug? If not, is there a workaround other than setting Project B to “Keep forever” and manually cleaning up releases?