Scalability of Octopus


We currently have an application setup within Octopus with many feature branches and a support branch being deployed to their own DEV/QA/UAT environments, using variable lists to control env specific updates to config files. This works fine.

However, we’re looking to bring other applications under Octopus control for deployment. What seems to be lacking is a concept of application group with isolated environments and variable lists. It is going to get complex to manage with large numbers of different environments and variable lists across many applications all within the same Octopus global views. I suppose we could install another Octopus server to provide segregation of Octopus envs and variable lists, but this is far from ideal. What approach do you suggest for managing the scaling of Octopus?