Using GitFlow in Azure DevOps (Does it mean multiple pipelines?)

Viewed 9239

Our dev team want to branch out (bad joke) into using a GitFlow like branching system where there would be a dev, uat and release branches(which would all need building from), I cant see a clever way of using the same pipeline to deploy different branches, could someone let me know the best way to do it? Is it literally create multiple pipelines for each branch needed?

1 Answers

No, you don't need to create multiple release pipelines.

I don't know what you do in the build pipelines, but in the release you can create one release pipeline with multiple "Stages" (for dev, UAT, and release), and multiple artifacts, in each stage and artifact, you can configure the branch, from which branch the artifacts will be.

See this configuration:

enter image description here:

enter image description here

Of course, you need to configure the triggers, you don't want to deploy the 3 stages immediately after release (you can also "play" with it, put the release stage after the UAT, for example).

Related