There may be a really obvious solution to this, but it has us stumped.
Within one of our projects, we have 23 separate applications/web services. When creating a release in our current non-Octopus deployment tool, the ‘user’ can choose which of these 23 apps they wish to deploy. The tool will then (one app at a time) stop the app pool, deploy the code and restart the app pool. It won’t go anywhere near the apps that weren’t selected for deployment.
How would we model this in OD?
We had thought of:
When creating a release, for any apps that aren’t to be deployed, select the ‘Last’ version for them and Octopus won’t deploy them. But how can we avoid Octopus running our steps to stop/start the app pool for those apps?
Create a stop/deploy/start step for each sub-app and the user manually chooses which of those 23 deploy steps that should/shouldn’t be executed in the Release setup. This would be a bit fiddly and error-prone.
I imagine this has been done over and over again by other people in OD, but we just can’t get our heads round it, so any help would be appreciated.