I am wondering how to handle production bug fixing. Our octopus project have several applications to deploy. We have different environment (dev, test, staging and production). One team for new feature and another for bug fixing and small improvement.
We create a new release for a new feature which generate a new application so a new step in our project.
When there is a bug to fix, the fix can be a code modification so a new nugget package or new variables and we have to create a new release in octopus.
Let’s say in production we have the release 1.0 and in dev we have the release 2.0. We create a release 1.0.1. how can i excute the deployment with the variables and process that was used for the release 1.0 and not use the ones uptodate (the 2.0) ?
The only way i see with the 2.6 version is :
- use octoclient to create a release with the same process/variables of an old release, do you have an example ?
- Create a new project and duplicates the variables (is there a way to clone a project in octopus ?)
I saw my problem would be solved with Branching support but i am looking for an alternative that i can implement more quickly.
thanks for your help