Azure DevOps多阶段部署Java Azure Function遇POM文件找不到错误

错误原因分析 #

你遇到的Not found mavenPOMFile错误，核心问题有两个：

1. Deployment Job默认不拉取代码：你使用的deployment类型任务，默认不会自动克隆代码仓库到代理机器，直接执行Maven任务自然找不到pom.xml文件。
2. 硬编码动态生成目录：流水线里写死了AzureServerless-1686925779077这个函数输出目录，这个名称是Maven构建时带时间戳动态生成的，每次构建都会变化，后续归档任务也会跟着失败。

优化后的流水线配置（推荐方案） #

把流水线拆分为构建和部署两个独立阶段，先统一完成代码构建并发布构件，再根据分支判断部署到对应环境槽，既解决路径问题，也避免重复执行构建逻辑：

trigger:
  branches:
    include:
      - release
      - master

stages:
  # 统一构建阶段：所有分支共享构建逻辑，生成并发布构件
  - stage: Build
    displayName: 'Build Java Function'
    jobs:
      - job: BuildJob
        displayName: 'Maven Build'
        pool:
          vmImage: 'ubuntu-latest'
        steps:
          - task: Maven@2
            displayName: 'Maven Package'
            inputs:
              mavenPomFile: 'pom.xml' # 若pom不在仓库根目录，改为实际路径
              goals: 'clean package' # 明确执行打包命令，确保生成函数产物
              publishJUnitResults: false

          # 复制函数构建产物，用通配符适配动态目录
          - task: CopyFiles@2
            displayName: 'Copy Function Artifacts'
            inputs:
              SourceFolder: '$(system.defaultWorkingDirectory)/target/azure-functions'
              Contents: '**/*' # 复制所有子目录及文件
              TargetFolder: '$(build.ArtifactStagingDirectory)/function'

          # 归档构件，避免硬编码目录名
          - task: ArchiveFiles@2
            displayName: 'Archive Function Package'
            inputs:
              rootFolderOrFile: '$(build.ArtifactStagingDirectory)/function'
              includeRootFolder: false
              archiveType: 'zip'
              archiveFile: '$(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip'

          # 发布构件到流水线制品库，供部署阶段使用
          - task: PublishPipelineArtifact@1
            displayName: 'Publish Build Artifact'
            inputs:
              targetPath: '$(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip'
              artifact: 'function-package'
              publishLocation: 'Container'

  # 部署到QA槽（仅release分支触发）
  - stage: DeployQA
    displayName: 'Deploy to QA Slot'
    dependsOn: Build
    condition: and(succeeded(), eq(variables['Build.SourceBranch'], 'refs/heads/release'))
    jobs:
      - deployment: DeployQAJob
        displayName: 'Deploy to QA'
        pool:
          vmImage: 'ubuntu-latest'
        environment: 'staging'
        strategy:
          runOnce:
            deploy:
              steps:
                # 下载构建阶段发布的构件
                - task: DownloadPipelineArtifact@2
                  displayName: 'Download Function Package'
                  inputs:
                    artifact: 'function-package'
                    path: '$(Build.ArtifactStagingDirectory)'

                # 部署到QA槽
                - task: AzureFunctionApp@2
                  displayName: 'Deploy to QA Slot'
                  inputs:
                    azureSubscription: 'xxxxxxxxxxxxxxxxxxxx'
                    appType: 'functionAppLinux'
                    appName: 'serverlesstest'
                    deployToSlotOrASE: true
                    resourceGroupName: 'pilot-rg'
                    slotName: 'qa'
                    package: '$(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip'
                    runtimeStack: 'JAVA|8'
                    deploymentMethod: 'auto'

  # 部署到生产槽（仅master分支触发）
  - stage: DeployProduction
    displayName: 'Deploy to Production Slot'
    dependsOn: Build
    condition: and(succeeded(), eq(variables['Build.SourceBranch'], 'refs/heads/master'))
    jobs:
      - deployment: DeployProductionJob
        displayName: 'Deploy to Production'
        pool:
          vmImage: 'ubuntu-latest'
        environment: 'production'
        strategy:
          runOnce:
            deploy:
              steps:
                # 下载构建构件
                - task: DownloadPipelineArtifact@2
                  displayName: 'Download Function Package'
                  inputs:
                    artifact: 'function-package'
                    path: '$(Build.ArtifactStagingDirectory)'

                # 部署到生产槽
                - task: AzureFunctionApp@2
                  displayName: 'Deploy to Production Slot'
                  inputs:
                    azureSubscription: 'xxxxxxxxxxxxxxxxxxxxxxxx'
                    appType: 'functionAppLinux'
                    appName: 'serverlesstest'
                    deployToSlotOrASE: true
                    resourceGroupName: 'pilot-rg'
                    slotName: 'production'
                    package: '$(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip'
                    runtimeStack: 'JAVA|8'
                    deploymentMethod: 'auto'

关键修改说明 #

1. 拆分Build/Deploy阶段：构建逻辑只执行一次，避免重复操作，同时彻底解决Deployment Job无代码的问题。
2. 通配符适配动态目录：不再硬编码函数输出目录，用**/*匹配所有内容，适配Maven动态生成的带时间戳目录名。
3. 流水线构件流转：构建阶段把打包好的zip发布到制品库，部署阶段直接下载使用，无需重复构建。
4. 明确Maven命令：添加goals: 'clean package'确保执行完整的打包流程，生成Azure Functions所需的运行产物。

临时应急方案（不推荐） #

如果不想调整流水线结构，可在每个Deployment Job的Maven任务前添加代码拉取步骤：

- checkout: self
  fetchDepth: 1

但这种方式会重复执行构建，效率较低，仅适合临时测试使用。

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