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?
As far as I can tell from the docs it is not possible to define multiple pipelines in a single .
Git Flow is an abstract idea of a Git workflow. It helps with continuous software development and implementing DevOps practices. The Git Flow Workflow defines a strict branching model designed around the project release. This provides a robust framework for managing larger projects.
Azure Pipelines combines continuous integration (CI) and continuous delivery (CD) to test and build your code and ship it to any target. Continuous Integration (CI) is the practice used by development teams of automating merging and testing code.
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:
:
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).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With