we have an application suite consisting of a number of databases, win services and web applications that are specific to a client.
We may have multiple clients using the same set of servers so the databases, win services and applications are installed with a client identifier.
Is there a way within the Octopus UI to collect this sort of information when deploying and including it as a variable in the deploy.
Thanks in advance
There is currently no way to supply a variable as part of a specific deploy, but you can create and assign variables to your project, and target them at a specific package/environment/machine.
The main issue you may have with doing this is that Octopus extracts packages to the same place - so when you deploy for Client A, it will go to C:/Octopus/Applications/Your.Package.1.0.0. When you deploy for Client B, it will also go to C:/Octopus/Applications/Your.Package.1.0.0. So any configuration changes you make for client B will override client A.
thanks for that.
So would a possible work around be to have a project per client with the variables set as required for that client?
In terms of the packages being extracted to the same place, that’s not a problem for us as differences are only in configuration.
Yes, multiple projects would be the best way, and will give you the best visibility for each client.
Octopus will soon include a feature for “cloning” projects which will make it easier for setting up new copies.