Allow using the same transforms for different environments
Octopus Deploy uses the Environment Name to select which configuration transform files will be applied. Say, for an environment with name "Dev", Octopus Deploy will automatically select Web.Dev.config from each nuget package.
I would like to be able to specify the 'configuration name' used by an Octopus Environment instead of using the default convention of using the Environment name, so I could have two different Octopus Environments, say "Dev1" and "Dev2", using the same configuration transforms, ie "Web.Dev.config".
The goal is to be able to deploy different releases to two identical environments without having to duplicate (identical) transformation files just to change the name 'Web.Dev1.config' and 'Web.Dev2.config'.
My configuration is:
- A single Octopus project
- Near 50 nuget packages (steps)
- Two development teams working in parallel on the same product
- Environments: Dev1, Dev2, QA, Staging, Production
We are integrating at the QA level, but each development team has its own copy of the Dev environment.
Sergio Acosta
shared this idea
-
Fredrik Aleksander Kristiansen commented
This feature would be very useful, as at my workplace, we have multiple testing environments, and would like to be able to use the same transform for all of them, and rather use variable substitution to fill in the values. The solution used now is creating copies of a common web.config file, and give it names like Web.Testing01.config, Web.Testing02.config etc, even though their content is the same used. I think it's best to keep the variables in octopus, that way you can do all configuration with octopus variables, instead of configuring them in your projects. When you have alot of projects, that should have common values when in the same environments, this works much better than doing the changes one time for each project