Confused about Release Changes listing

Using Version 2019.12.6 of Octopus server.

We are running Octopus on a Windows VM, configured with multiple tenants, one for each client, and set up to deploy to a UAT environment, which can promote to Production.

Looking at a recent deployment for one tenant (tentatively renamed to “OrangeUnderwriting” for anonymity), the “Changes” list is listing another release for a completely different tenant. This caused much worry and confusion as to whether our Orange client was receiving an update for work intended for another client.

After digging through our dev-ops pipeline we are satisfied that the two builds are indeed correct, but we are still left confused as to why the Release Task for “Orange” is listing a deployment that is deployed to our other tenant, “Banana”.

Any insight will be appreciated.

Hi Wesley,

Thanks for getting in touch!

The deployment notes information summarises all releases made to that environment since the last deployment. So, if you have tenant-specific releases and those tenants are all in the same environment, Octopus will assume that all of the releases are part of the same “branch” and summarise them together.

If this is something that you will be doing on a regular basis, you could consider using pre-release versioning for any single tenant only releases. These releases would then be excluded from the deployment notes summary.

I hope this helps, please let me know if you have any further questions.

Best regards,