Octopus tries to delete releases from different channels

Legacy Uncategorised
1

I have several channels for on project. Lets name channels: default, A and B.

When I install release to channel A and then have several new releases to channel B, Octopus tries to delete last release on channel A (probably due to retention policy).

I consider this as a bug or undocumented feature. But if Octopus will not take into account different channels for retention policy, then channels are totally worthless for me :frowning:

How to solve problem? I wan’t that retention policy is taken independently for each channel releases.

2

Hi Valdis,

Thanks for getting in touch! I cannot replicate this behaviour. I have two channels, and I had my retention set to 1 and I couldn’t get it to delete one channel that was very behind the versions of the other channel. Please see my screenshots. As you can see from the retention task, it treats all channels as individual projects and has two listings for Super Awesome Project keeping 1 release in prod independent of each other.

Are you able to give me specific instructions on how to replicate this? Could the delete have happened in some other way? Can you check from either the tasks or audit log? What version are you using? (I don’t believe we changed this since the release of the feature, but I would like to test on your version).

Let me know what you find!
Vanessa

lifecycle-settings.png
lifecycle-settings.png1100×517 61.9 KB

channel-lifecycle-settings.png
channel-lifecycle-settings.png1016×454 46.8 KB

releases-list.png
releases-list.png791×523 50.5 KB

retention-policy-logs.png
retention-policy-logs.png1028×496 136 KB

3

Hi!

I will try to figure out from logs what actually was done and come back.

4

Hi!

Seams that I was wrong. Sorry. Problem is closed everything works as expected.

5

Hi Valdis,

Great to hear it!

Vanessa

6

Hi,

I’m having the same issue. Compared to your screenshots I use a different lifecycle for each channel. Could that be a problem?

Best regards,

Maarten

7

Hi Maarten,

It shouldn’t. Could you send me through a retention policy log to have a look to see what might be going on?
Feel free to email it to support at octopus dot com if you prefer.

Vanessa

8

Hi Vanessa,

I just have send an e-mail to support. I will report the outcome here when someone else is having the same issue.

Best regards,

Maarten

9

Hi,

After contacting the support desk, Vanessa explained that I could create a variable Octopus.Tentacle.CurrentDeployment.RetentionPolicySubset with the value #{Octopus.Release.Channel.Id

As she explained: This will group your deployments by channel ID for where they use the same package ID

So if someone else is facing this issue, this works :slight_smile:

10

Hi,

Unfortunately I have the same issue on Octopus 3.3.20. Our configuration are following:
Channel: A, Lifecycle: Test
Channel: B, Lifecycle: Test
Policy retention: keep one release
When I make deploy for channel A with release A during at last step of retention policy for some reason it removes releases from B channels.