We’re looking to fully automate build process with TeamCity + Octopus. One of the current hurdle is that we have to prep and package up deployments for different clients. The preping part is where I have some questions as to how Octopus fits in. Currently, we have a master staging site that everything goes to for clients to preview. When it’s ready to be released to the various production environments, we:
- We strip out a lot irrelevant configurations for particular production servers (eg: logins, passwords, etc. )
- We strip out aspx section/sites that may not apply for particular clients
The idea of having 1 release code base to push out is nice, but I’d like to make sure unnecessary data is NOT leaked to the client’s production machine. Could someone help explain how, assuming it’s possible, Octopus could make this work?