Loading

What information to collect for Mule Maven or CI/CD build issues

Publish Date: Aug 24, 2024
Task

GOAL

The objective of this article is to document the information that needs to be collected to effectively investigate issues related to the application build and deployment using the Mule Maven Plugin. This will help us expedite the troubleshooting process.
Steps

Please capture and share the below mentioned required information as per the issue category.
 

#IssueIssue DescriptionRequired Information
1The asset publish failure to Anypoint ExchangeThe publish failure to the Anypoint Exchange.
  1. Asset's pom.xml file
  2. Parent pom.xml file (if used)
  3. re-run Maven build with debug enabled (mvn -X) and share the console output full log file
  4. The settings.xml file (i.e., located in Windows C:\users\<user_name>\.m2\ folder OR Mac/Linux ~/.m2/settings/xml)
  5. Maven deploy command used
2The application deployment failure Anypoint Runtime ManagerThe application deployment failure to the Anypoint Runtime manager (Hybrid/ Cloudhub/ RTF/ Cloudhub 2.0)
  1. Application's pom.xml file
  2. Parent or domain project's pom.xml file (if used)
  3. run Maven with debug enabled (mvn -X) and share the console output full log file
  4. The settings.xml file (i.e., located in Windows C:\users\<user_name>\.m2\ folder OR Mac/Linux ~/.m2/settings/xml)
  5. Maven build command
3401 Unauthorized errorGetting 401 Unauthorized error when publishing an asset to Exchange or Deploying an application
  1. Project's pom.xml file
  2. run Maven build output console log file
  3. The settings.xml file (i.e., located in Windows C:\users\<user_name>\.m2\ folder OR Mac/Linux ~/.m2/settings/xml)
  4. If user/service account credentials are used for authentication, share the User id
  5. If Connected apps credentials are used for authentication, share the screenshot of its scope
Knowledge Article Number

001116821

 
Loading
Salesforce Help | Article