Release Branches


I’m just beginning to set up Octopus Deploy to do our deployments - currently TeamCity does all this as well as building. The way we work is that we have a master branch and also a release branch (as described here:

What we currently do is deploy any changes in master to one environment (MASTER) and any changes in our current release branch to another environment (BRANCH) with branch eventually being promoted to the production environment (which has multiple different regions). I can’t really see any documentation on setting Octopus up this way but the docs do suggest it’s possible.

I’ve already got a project setup in Octopus to deploy to master whenever a successful build is completed on TC. TC packages everything up and creates a release in Octopus. I’m just trying to do the branch part now but I can’t get it to work.

Any help would be appreciated.

Hi Colin,

Thanks for getting in touch! It looks like what you are after is either our Channel feature our Multi-tenancy. Either of these will work for what you want to do.

The documentation page you linked is a good start and directs you towards using Channels which is what we would recommend in your situation. You can configure your release to be automatically deployed to the desired branch as soon as a change is made to master.

We have a more comprehensive walkthrough on using them over here:
And some more documentation (mostly the same information) here:

The other option is to configure a Tenant per feature/branch. This is a great alternative to Channels and will give you the same results.

We also have a really nice blog post on our Multi-Tenancy feature that is absolutely worth reading.

For what ever method you decide to go with, if you have any questions at all, or run into any issues. Please feel free to get in touch and we will be able to help you out.

Let me know how you go. :slight_smile:

Best Regards,