Azure DevOps部署作业无法跨作业获取输出变量问题

我在第二个部署作业Deploy_Infrastructure中，通过dependencies引用第一个部署作业FetchAppRegistration的输出变量AppClientId，但始终获取不到值。使用表达式$[dependencies.FetchAppRegistration.outputs['Fetch_Azure_AD.AppClientId']]返回空内容，参考官方文档后仍未解决。

流水线日志显示：FetchAppRegistration已成功找到Azure AD应用并设置AppClientId变量，但Deploy_Infrastructure的调试日志里App Client ID为空，导致执行deploy.ps1时提示'existingAppClientId'参数缺失。

完整流水线代码如下：

parameters:
  environment: ''
  serviceConnectionName: ''

jobs:
- job: Build
  displayName: 'Build Job'
  steps:
    - script: echo "Building the application..."
      displayName: 'Execute build'

- deployment: FetchAppRegistration
  displayName: 'Fetch Azure AD App Registration Client ID'
  environment: ${{ parameters.environment }}
  dependsOn: Build
  strategy:
    runOnce:
      deploy:
        steps:
          - checkout: self
          - task: AzurePowerShell@5
            name: Fetch_Azure_AD
            displayName: 'Fetch Azure AD App Registration Client ID'
            inputs:
              azureSubscription: ${{ parameters.serviceConnectionName }}
              ScriptType: 'InlineScript'
              Inline: |
                $appName = "msys-azure-${{ parameters.environment }}".ToLower()
                Write-Host "Fetching Azure AD App with display name: $appName"
                $app = Get-AzADApplication -DisplayName $appName
                if ($app -eq $null) {
                  Write-Error "Application not found: $appName"
                  exit 1
                }
                $appId = $app.AppId
                Write-Host "Application found. AppId: $appId"
                Write-Host "##vso[task.setvariable variable=AppClientId;isOutput=true]$appId"
                Write-Host "Setting variable AppClientId to: $appId"
              azurePowerShellVersion: 'LatestVersion'
              pwsh: true

- deployment: Deploy_Infrastructure
  displayName: 'Deploy Infrastructure'
  dependsOn: FetchAppRegistration
  condition: succeeded()
  environment: ${{ parameters.environment }}
  variables:
    AppClientId: $[dependencies.FetchAppRegistration.outputs['Fetch_Azure_AD.AppClientId']]
  strategy:
    runOnce:
      deploy:
        steps:
          - download: current
            artifact: drop
            displayName: Download artifacts
          - script: |
              echo "App Client ID: $(AppClientId)"
            displayName: 'Debug App Client ID'
          - task: AzurePowerShell@5
            displayName: 'Deploy Azure Infrastructure'
            inputs:
              connectedServiceNameARM: ${{ parameters.serviceConnectionName }}
              azurePowerShellVersion: 'LatestVersion'
              ScriptPath: '$(Pipeline.Workspace)/drop/deploy/deploy.ps1'
              ScriptArguments: 
                -resourceGroupName $(ResourceGroupName) `
                -existingAppClientId $(AppClientId)

原因分析 #

当部署作业（deployment类型）关联environment时，输出变量的引用路径会因为环境资源的存在而发生变化，原有的dependencies引用格式无法正确定位到输出变量。

解决方法 #

方法1：改用作业级别的变量引用格式 #

直接使用jobs前缀替代dependencies，修改Deploy_Infrastructure中的变量定义：

variables:
  AppClientId: $[jobs.FetchAppRegistration.outputs['Fetch_Azure_AD.AppClientId']]

这种方式无需考虑环境资源的影响，适用于绝大多数部署作业间的变量传递场景。

方法2：使用包含环境资源的完整路径 #

如果需要明确指定环境资源，可在引用路径中添加环境资源名称（可在流水线运行日志的FetchAppRegistration作业详情中查看资源名称）：

variables:
  AppClientId: $[dependencies.FetchAppRegistration.outputs['<环境资源名称>.Fetch_Azure_AD.AppClientId']]

额外验证步骤 #

• 确认Fetch_Azure_AD任务的name属性拼写正确，输出变量是绑定到该任务名称下的
• 检查Write-Host "##vso[task.setvariable variable=AppClientId;isOutput=true]$appId"命令，确保isOutput=true参数存在且无拼写错误
• 在Deploy_Infrastructure的调试步骤中添加以下脚本，排查依赖输出的完整内容：

echo "Full dependencies outputs: $($dependencies.FetchAppRegistration.outputs | ConvertTo-Json)"

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