CI/CD for MuleSoft Applications (Course #cicd)

Programme every line is something you do

6 modules · 18 topics · in course-flow order

1. Module 1

   Same commit, same artifact

   Objective. Industrialize Maven builds with locked versions and managed repositories so any commit rebuilds the identical deployable artifact.

   • Structure a Mule Maven project: parent POM, pinned mule-maven-plugin version, per-environment profiles for properties
   • Serve all dependencies from a private Nexus or Artifactory mirror — no direct internet or Exchange pulls on build agents
   • Guarantee reproducibility: promote the tested binary through stages instead of rebuilding it per environment
2. Module 2

   Pipeline stages that pay off

   Objective. Assemble the canonical Mule pipeline so every branch crosses identical automated stages whichever CI engine runs them.

   • Weigh Jenkins, Azure DevOps, GitLab CI and GitHub Actions on Mule plugins, agent sizing and supported Exchange authentication
   • Script the sequence build → MUnit → governance checks → sandbox deploy → smoke tests, targeting under 15 minutes end to end
   • Hold Anypoint credentials as CI secret variables from a dedicated connected app — never inline in pipeline YAML
3. Module 3

   Deploy by pipeline, revert by pipeline

   Objective. Drive CloudHub and Runtime Fabric releases from the CLI so promotion and rollback execute hands-free with health checks.

   • Deploy to CloudHub from the pipeline (Anypoint CLI or Maven plugin): region, worker size, autoscale, per-env properties
   • Release to Runtime Fabric through CI: images pulled from the artifact registry with CPU/memory limits set per application
   • Automate rollback: redeploy the previous artifact within 5 minutes and hold traffic until health probes pass
4. Module 4

   Promote artifacts, not hope

   Objective. Design dev-to-production promotion so only tested, approved binaries move and configuration alone varies per environment.

   • Promote one immutable binary Dev → QA → Staging → Prod, injecting secure properties at deploy time, never baked in
   • Gate production promotion behind a two-person approval recorded in the pipeline audit trail (target: 100% of prod deploys)
   • Align application versions with API Manager versions semantically so pipeline tags and gateway contracts stay in sync
5. Module 5

   Platform setup as reviewed code

   Objective. Codify Anypoint resources in version-controlled repositories so platform changes travel through pull requests like code.

   • Declare API Manager assets — API versions, policies, SLA tiers — through Anypoint Platform APIs executed by the pipeline
   • Peer-review infrastructure changes with a PR template covering impact, rollback plan and affected environments
   • Detect configuration drift with scheduled jobs diffing live platform state against the declared baseline
6. Module 6

   Merge blocked unless proven

   Objective. Enforce MUnit suites and coverage gates in CI so regressions die in the build before reaching any shared environment.

   • Run MUnit headlessly in CI with parallel suites and publish failure reports as pipeline artifacts
   • Enforce coverage gates that fail the build — e.g. 75% overall, 100% on error paths — rather than cosmetic reports
   • Fail fast: quarantine flaky tests, keep main permanently green and cap automatic re-runs at one attempt

References & Official Documentation every claim above has a source

Module 1

• Maven ReferenceMuleSoft Docs
• Mule Maven PluginMuleSoft Docs

Module 2

• Connected Apps in Anypoint PlatformMuleSoft Docs

Module 3

• Deploy Applications to CloudHub 2.0 Using the Mule Maven PluginMuleSoft Docs
• Deploying Mule Apps to Runtime Fabric Using Anypoint CLIMuleSoft Docs

Module 4

• Secure Configuration PropertiesMuleSoft Docs

Module 5

• Anypoint CLI for API ManagerMuleSoft Docs

Module 6

• MUnit Maven Configuration for CoverageMuleSoft Docs

More in Operations / DevOps