Using channels to deploy selected releases to selected tenants

operations's Avatar


10 Jul, 2017 12:46 AM

I'm not sure how most people use this type of configuration, but I'll try my best to explain the way we have set up Octopus. We have many different release branches of the software that we deploy using Octopus, and these different releases are deployed to different tenants. So we have configured multiple channels, each with a different version filter in order to easily create the correct release for the channel.
We have also created a Customer tenant tag, which allows us to scope each channel to a list of tenants that are allowed to receive releases from this channel.
Now the problem we face, is that when you go to deploy a particular release from a particular channel, the default Octopus behaviour is that when you select the desired environment to be deployed to, these Customer tenant tags are all included for this deployment, so we may have 10 matching tenants, and if these are not de-selected, then all 10 will be deployed to at the same time, which is NOT what we are intending, and unfortunately we have had occasions where our users have accidentally deployed a release to multiple tenants at once.
The way we would like to see this work, is that the tenant tags used to restrict the deployment of a channel would instead make up the list of tags available on the release deployment screen to be deployed to, so rather than all of them being automatically selected, when you initially select the deployment environment, NO tenants are included by default. Then the user could select the desired tenant either by using the Tenants drop-down, or selecting from the available tenant tags. This way they could then either just select the one to deploy to, or multiple if that is what is desired, rather than having all of them automatically selected by default.
At the moment on the deployment screen, not only can we select the tenant tags used to restrict the channel, we can also select any of the other tenant tags which are pointless, as they are not able to receive the release from this channel. I've attached an example of this that shows 6 of the Customer tenant tags selected, but there are only 3 matching tenants, which are the ones included on the channel restrictions. This tenant tag should be filtered to restrict selections to only those defined on the channel.
It's confusing to try and get this across in words, but what are your thoughts on this approach? Is this not how most people would intend to use this type of configuration?

  1. Support Staff 1 Posted by Daniel Fischer on 12 Jul, 2017 06:56 AM

    Daniel Fischer's Avatar

    Hi Simon,

    Thanks for your thoughts here. I have run this past our developers and we are currently discussing options/ideas/thoughts. I'll update as soon as I have some more information. Just thought I would let you know that I've not forgotten about your question here.

    Best regards,

  2. 2 Posted by operations on 12 Jul, 2017 07:22 AM

    operations's Avatar

    Thanks Daniel - Let me know if I need to elaborate further to make anything clearer!

  3. Support Staff 3 Posted by Daniel Fischer on 13 Jul, 2017 08:45 AM

    Daniel Fischer's Avatar

    Hi Simon,

    Thanks for waiting here. So it looks like we are going to make a little bit of change here. We are going to change it so we no longer auto-fill this section. We are also going to do a check to ensure that only tags relevant to the channel you created the release with can be listed.

    You can follow the issue here:

    Let me know what you think.:)

    Best regards,

  4. 4 Posted by operations on 16 Jul, 2017 11:31 PM

    operations's Avatar

    Thanks Daniel, that sounds perfect! I look forward to that being implemented, it will help us greatly.
    Cheers, Simon.

  5. Support Staff 5 Posted by Daniel Fischer on 17 Jul, 2017 06:57 AM

    Daniel Fischer's Avatar

    Hi Simon,

    No worries, feel free to get in touch at any time. :)

    Best regards,

  6. Paul Stovell closed this discussion on 31 Oct, 2017 08:14 PM.

  7. operations re-opened this discussion on 13 Feb, 2018 05:28 AM

  8. 6 Posted by operations on 13 Feb, 2018 05:28 AM

    operations's Avatar

    Hi Guys - We're finally looking at upgrading our Prod site from 3.15.7 to the latest release, and I was just reviewing this issue. I'm pretty sure this was implemented at some point along your release path, but checking the latest version it appears that either it was not implemented, or it has gone back to the original behaviour. If I now go to deploy a release for a particular channel that has tag restrictions, these tags are pre-filled on the deployment screen, and you can also select other tags that are not available in the channel definition. So at this stage the default deployment would still deploy to multiple matching tenants, unless these tags are removed first and the desired tenants selected.
    The available tenants filter is correct, and only shows tenants that match the channel restrictions, but even selecting one tenant from this filter will still deploy to multiple tenants unless the pre-filled tags are first removed.
    Looking at the github issue you listed above, it appears this was brought in for version 4.0.0 back in October last year, has this behaviour been reversed?

  9. 7 Posted by operations on 14 Feb, 2018 10:41 PM

    operations's Avatar

    Also, In addition to this, if you filter the Project Overview screen to a specific Release, then click the DEPLOY button for a specific Tenant/Environment, it should take you to the Create Deployment screen for just that one tenant, but because the deployment screen is auto-filled with the Channel-defined Tags, it may default to creating multiple deployments instead of the single one you were intending. You then have to remove the Tags to get rid of the extra deployments.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Already uploaded files

  • Channel_tenants.JPG 34.8 KB

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac