Path: Delivering MuleSoft applications with Azure DevOps · Part 4 of 4
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.
Path: Delivering MuleSoft applications with Azure DevOps · Part 1 of 4
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.
Path: Delivering MuleSoft applications with Azure DevOps · Part 2 of 4
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.
Path: Delivering MuleSoft applications with Azure DevOps · Part 3 of 4
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.
