Allow non-tenant and multi-tenant deployments to the same environment
The new 3.4 Multi-tenancy feature is great. But there is a limitation preventing it for some to use it effectively.
We have several projects, some have multi-tenant deployments (per client) some others not (tool project, shared services projects etc).
We deploy all these projects to the same test and staging servers and some as well to production environment. Meaning, the same machine might be used for multi-tenant and non-tenant deployments.
The current 3.4 release does not allow us to use the same environment/target for both type of projects.
Workaround as published (setup dummy tenant instance) is a less desirable, as we would need to reconfigure too many projects to use the dummy-tenant; Next to that it also sort of makes history and promotion of releases over environments less nice (redo releases using this dummy-instance just to be able to promote the correct instance up.
Workaround is definitely possible, but a nice fix (just allow mixed types of tenant-non-tenant projects to the same environment by configuration is preferable.
Henk-Jan Meulekamp
shared this idea
Happy to share that this is now available in 3.15.
See our blog post for more information – https://octopus.com/blog/octopus-release-3-15
-
Thomas Illingworth
commented
This is currently raised here:
https://github.com/OctopusDeploy/Issues/issues/2722In one of my comments I suggested that you could consider this a bug as the workaround we're currently using on some environments is to configure multiple deployment targets to the same server. This works but obviously uses more licences (2 per server) which is the major problem if you have a lot of servers to deploy to.