MuleSoft Integration

Build and deploy MuleSoft applications to CloudHub, Anypoint Runtime Fabric, or on-premise MuleSoft servers using Opsera's pipeline automation.

Prerequisites

• MuleSoft account credentials saved as an Opsera Pipeline Parameter in Tool Registrypom.xmlpresent in the Mule project folder in the SCM repository

• MuleSoft Job configured in Opsera (Tool Registry → open tool → Jobs tab)SCM repository with MuleSoft project registered in Tool Registry

Pipeline setup

1

Create MuleSoft job in Tool Registry

Tool Registry → open configured tool → Jobs tab → New Job. Set Job Type = Build, choose Build Type and Agent Label.

2

Create pipeline and add step

Pipelines → New Pipeline → Blank Template. Configure Step Setup: Name, Tool, Step Type.

3

Configure step settings

Select the tool, set Job Type to Opsera Managed Job. Choose VCS, repository, and branch. Select the MuleSoft parameter from Parameter Settings and add runtime argument commands. Set Output File Path and File Name.

4

Run and review

Click Start Pipeline. Navigate to Summary → Pipeline Logs → Console Output for the full execution log.

Points to remember

• Thepom.xmlfile must be present in the Mule project folder in your repository — it stores all project dependencies and MuleSoft hosting environment information.

• MuleSoft credentials should always be stored as Opsera Pipeline Parameters — never hardcoded in commands or scripts.

• Alternatively, project dependencies can be added as Opsera Parameters instead of maintaining them in pom.xml — useful for environment-specific overrides.