Hi
Our deployment path from development through to test and production is fairly stock standard. My question is regarding a deployment strategy for a “fixes/patches” environment in the situation where the main environment are already been provisioned for the next release. i.e. you want to make a small fix to production by leapfrogging any new work that is already on the test site. I could create an additional “fixes” project in Octopus, but how would I configure it to deploy to the same production site as the main Octopus project? I have been using a naming convention of “clientname.#{Octopus.Environment.Name}” i.e. clientname.test and clientname.production, but what I’d also need is clientname.test.fixes and clientname.production
Thanks