Azure Pipeline构建卡在Maven阶段提示未指定构建目标报错

在Azure Pipeline中执行Mule项目构建时，流程运行到Maven阶段卡住无法推进，最终返回如下错误：

[ERROR] No goals have been specified for this build. You must specify a valid lifecycle phase or a goal in the format : or :[:]:. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]

对应项目pom.xml配置如下：

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>com.mycompany</groupId>
    <artifactId>clx-salesforceupsert-ifa</artifactId>
    <version>1.0.0-SNAPSHOT</version>
    <packaging>mule-application</packaging>

    <name>clx-salesforceupsert-ifa</name>

    <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>

        <app.runtime>4.4.0-20220221</app.runtime>
        <mule.maven.plugin.version>3.5.4</mule.maven.plugin.version>
    </properties>

    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-clean-plugin</artifactId>
                <version>3.0.0</version>
            </plugin>
            <plugin>
                <groupId>org.mule.tools.maven</groupId>
                <artifactId>mule-maven-plugin</artifactId>
                <version>${mule.maven.plugin.version}</version>
                <extensions>true</extensions>
                <configuration>
                <cloudHubDeployment>
                <uri>https://anypoint.mulesoft.com</uri>
                <server>${server}</server>
                <muleVersion>${app.runtime}</muleVersion>
                <applicationName>${app.name}</applicationName>
                <workers>${workers}</workers>
                <workerType>${workerType}</workerType>
                <environment>${environment}</environment>
                <objectStoreV2>true</objectStoreV2>
                
                </cloudHubDeployment>
                </configuration>
            </plugin>
            
        </plugins>
    </build>

    <dependencies>
        <dependency>
            <groupId>org.mule.connectors</groupId>
            <artifactId>mule-http-connector</artifactId>
            <version>1.6.0</version>
            <classifier>mule-plugin</classifier>
        </dependency>
        <dependency>
            <groupId>org.mule.connectors</groupId>
            <artifactId>mule-sockets-connector</artifactId>
            <version>1.2.2</version>
            <classifier>mule-plugin</classifier>
        </dependency>
    </dependencies>

    <repositories>
        <repository>
            <id>anypoint-exchange-v3</id>
            <name>Anypoint Exchange</name>
            <url>https://maven.anypoint.mulesoft.com/api/v3/maven</url>
            <layout>default</layout>
        </repository>
        <repository>
            <id>mulesoft-releases</id>
            <name>MuleSoft Releases Repository</name>
            <url>https://repository.mulesoft.org/releases/</url>
            <layout>default</layout>
        </repository>
    </repositories>

    <pluginRepositories>
        <pluginRepository>
            <id>mulesoft-releases</id>
            <name>MuleSoft Releases Repository</name>
            <layout>default</layout>
            <url>https://repository.mulesoft.org/releases/</url>
            <snapshots>
                <enabled>false</enabled>
            </snapshots>
        </pluginRepository>
    </pluginRepositories>

</project>

报错核心原因是执行Maven命令时未指定任何构建生命周期阶段或插件目标，Maven无法识别需要执行的操作直接抛出错误，感知上的"卡顿"是流水线任务状态同步延迟导致的表象，和当前pom里的依赖、仓库、Mule插件配置没有直接关系。
常见触发场景有两个：

• Azure Pipeline的Maven任务配置中，Goals输入项留空，没有传入需要执行的构建指令
• 流水线脚本中调用mvn命令时漏写目标参数，仅执行了mvn没有追加后续阶段参数

• 修正Azure Pipeline的Maven任务配置
  打开流水线的Maven任务配置页，在Goals输入框填入Mule项目对应构建目标：仅做项目打包时填clean package，需要构建完成后自动部署到CloudHub时填clean deploy。
  如果使用YAML编写流水线，对应Maven任务参考配置如下：

  - task: Maven@3
    inputs:
      mavenPomFile: 'pom.xml'
      goals: 'clean package' # 根据部署需求替换为deploy等目标
      publishJUnitResults: true
      testResultsFiles: '**/surefire-reports/TEST-*.xml'
      javaHomeOption: 'JDKVersion'
      jdkVersionOption: '1.8' # Mule 4.4版本适配JDK 1.8
  

• 配置pom默认构建目标（可选优化）
  如果需要直接执行mvn命令不追加参数也能完成构建，可以在pom的build节点下增加默认目标配置，原有插件、依赖配置不需要改动：

  <build>
      <defaultGoal>clean package</defaultGoal>
      <!-- 原有plugins等配置保持不变 -->
  </build>
  

• 校验参数传递逻辑
  如果是通过流水线变量动态传递Maven目标，需要检查对应变量在Maven任务执行阶段是否被正确赋值，避免变量值为空导致最终执行的mvn命令缺失目标参数。

内容的提问来源于stack exchange，提问作者Niladri dey