← Blog

Article series · 4 articles

Delivering MuleSoft applications with Azure DevOps

From branching strategy to CloudHub 2.0 deployment: GitFlow, Maven versioning, pipeline templates and approvals, in that order.

Start with the first article →

Reading order

  1. Part 1 of 4

    GitFlow for MuleSoft: branch rules a pipeline can act on

    Why GitFlow still fits scheduled MuleSoft releases, where it doesn't, and how to turn branch names into pipeline behaviour — with a working reference project.

  2. Part 2 of 4

    Versioning Mule applications with the Maven release plugin in Azure Pipelines

    release:prepare and release:perform explained step by step, running inside Azure Pipelines — detached HEAD, pushing with the pipeline token, [skip ci] and branch protection.

  3. Part 3 of 4

    Azure Pipelines templates for MuleSoft: one delivery flow, many applications

    How to structure versioned Azure Pipelines templates for Mule applications — stages, jobs and steps, secrets without secure files, and why MUnit is left out of a public pipeline.

  4. Part 4 of 4

    Deploying to CloudHub 2.0 from Azure Pipelines: build once, approve, verify

    Promote the same Exchange artifact through test, uat and prod on CloudHub 2.0, with approvals on Azure DevOps environments and a smoke test after every deployment.