We use Team Visual Studio Services .
We have a Prod-Branch created by our Prod-Build-Definition and deployed by our Prod-Release-Definition into our test / integration and production environment.
Each time we deploy Prod-Release to the client, we create the Prod-Rel-Version-xxx branch from Prod-Branch (in case this is necessary for the correction).
During Sprint, we develop Dev-Branch, which is built according to our Dev-Build-Definition and deployed by our Dev-Release-Definition to our DEV for developer tests.
After Sprint (or from time to time), Dev-Branch merges into Main-Branch and then into Prod-Branch. From there, the client goes to various stages of testing.
When there is a fix, we fix the error in the Prod-Rel-Version-xxx branch and would like to reuse the existing existing Prod-Build-Definition to create this version of the fix and deploy the existing Prod-Release-Definition at different stages for testing and transition from this version.
How can we reuse our Prod-Build-Definition with this other branch (Prod-Rel-Version-xxx Branch instead of Prod-Branch)?
When I look at the definition of an assembly, I think it would be possible just to edit the server path (repository> mappings) from $/NameOfOurApp/Prodto $/NameOfOurApp/Prod-Rel-Version-x.x.x)... which should do the trick or not? But from what I read, it is not possible to use Build-Variables in server mappings, so I cannot change this variable, for example, in the New Build Dialog ...
?