Tenants on separate instances

I have a setup where each tenant has their own folder for their web app, each with their unique connection string. They are on the same version of the product, but we have to isolate them due to client requirements. How can I create a single release that could deploy our changes to all clients and run the client-specific transforms on the web.config files for connection strings?

Hi Jacob,

Thanks for getting in touch.

Assuming you are using our Tenants feature, all you have to do is configure additional transforms with a tenant-specific variable, use tenant-specific variables for your paths and you should be good to go.

For example, if you’ve got configs that have the tenant-id in the name, then when you provide your own transformation files, you would use a variable replacement to pick the config that you’re after. This documentation on working with tenant-specific variables will help explain it in more detail.

Let me know how you go.


This looks exactly like what I was looking for. Phew. Thanks.

Do I need to purchase a specific instance in order to see the tenants menu
item? It does not show by default. I’m using Octopus 3.5.7

Sorry, I didn’t realize there was a configuration option to enable multiple
tenants. Thank you for your help you can close this issue.