GitHub actions CI/CD pipeline for MuleSoft

[Blog post + video] Part 1: How to set up a CI/CD pipeline to deploy your MuleSoft apps to CloudHub using GitHub Actions
[Blog post + video] Part 2: CI/CD pipeline with MuleSoft and GitHub Actions - secured/encrypted properties
[Blog post + video] Part 3: CI/CD pipeline with MuleSoft and GitHub Actions - MUnit testing
[Blog post + video] Part 4: CI/CD pipeline with MuleSoft and GitHub Actions - MUnit minimum coverage percentage
[Blog post + video] Part 5: CI/CD pipeline with MuleSoft and GitHub Actions - Enabling MFA through a Connected App

Note

This is a simple Mule application to test. Please update the app.name and env properties from the pom.xml to your own.

Branches

Different examples are being demonstrated per branch. Here's the summary of each.

	`main`	`connected-app`	`cloudhub2`
Deployment	CH1	CH1	CH2
Passing secured properties	✅	✅	✅
MUnit testing in pipeline	✅	✅	❌
Running MUnit coverage	✅	✅	❌
Nexus credentials	✅	✅	❌
Auth	username/password in `pom.xml`	connected app in `pom.xml`	server in `settings.xml` (using connected app)
Maven version	`3.8.0`	`3.8.0`	`4.1.1`
Runtime	`4.4.0` through the `muleVersion` property	`4.4.0` through the `muleVersion` property	`4.4.0` through the `releaseChannel` property (`NONE`)

The initial versions of the pipeline are based on the following repository created by Archana Patel: arch-jn/github-actions-mule-cicd-demo.