Azure DevOps YAML自动发现解决方案文件并批量执行任务失败求助

Azure DevOps YAML的${{ each }}属于编译时表达式，在流水线启动前就会完成解析。而你通过PowerShell任务设置的输出变量是运行时生成的，编译阶段根本无法读取到这个变量的值，因此后续的循环任务不会被生成。

把单解决方案的构建逻辑抽成独立模板，再通过PowerShell在运行时生成对应构建阶段，完美适配自动发现的场景。

步骤1：创建构建模板文件（build-solution.yml） #

parameters:
  - name: SolutionName
    type: string
  - name: ContinueOnError
    type: boolean
    default: true
  - name: Clean
    type: boolean
    default: true

steps:
  # NuGet还原
  - task: NuGetCommand@2
    displayName: "Nuget restore ${{ parameters.SolutionName }}"
    inputs:
      command: "restore"
      restoreSolution: "Solutions/${{ parameters.SolutionName }}"
      noCache: true
    continueOnError: ${{ parameters.ContinueOnError }}

  # VSBuild构建
  - task: VSBuild@1
    displayName: "Build ${{ parameters.SolutionName }}"
    inputs:
      solution: Solutions/${{ parameters.SolutionName }}
      clean: true
      restoreNugetPackages: true
    continueOnError: ${{ parameters.ContinueOnError }}

  # Git清理（按需执行）
  - task: PowerShell@2
    condition: and(succeeded(), eq('${{ parameters.Clean }}', 'True'))
    displayName: "Git clean -xdf after ${{ parameters.SolutionName }}"
    inputs:
      targetType: "inline"
      script: |
        git clean -xdf
    continueOnError: ${{ parameters.ContinueOnError }}

步骤2：修改主流水线文件 #

parameters:
  - name: SolutionPath
    type: string
    default: '$(System.DefaultWorkingDirectory)\Solutions'
  - name: SolutionFilter
    type: string
    default: "*.sln"
  - name: ContinueOnError
    type: boolean
    default: true
  - name: Clean
    type: boolean
    default: true

stages:
  # 阶段1：自动发现所有解决方案
  - stage: DiscoverSolutions
    jobs:
      - job: Discover
        steps:
          - powershell: |
              $path = '${{ parameters.SolutionPath }}'
              $filter = "${{ parameters.SolutionFilter }}"
              $slnFiles = Get-ChildItem -Path $path -Filter $filter | Select-Object -ExpandProperty Name
              
              # 生成每个解决方案对应的构建阶段JSON
              $stages = @()
              foreach ($sln in $slnFiles) {
                $stageId = $sln -replace '\.sln$',''
                $stage = @{
                  stage = "Build_$stageId"
                  jobs = @(
                    @{
                      job = "Build_$stageId"
                      steps = @(
                        @{
                          template = 'build-solution.yml'
                          parameters = @{
                            SolutionName = $sln
                            ContinueOnError = ${{ parameters.ContinueOnError }}
                            Clean = ${{ parameters.Clean }}
                          }
                        }
                      )
                    }
                  )
                }
                $stages += $stage
              }
              
              # 将阶段定义转为JSON并输出为变量
              $stagesJson = $stages | ConvertTo-Json -Depth 10
              Write-Host "##vso[task.setvariable variable=buildStages;isOutput=true]$stagesJson"
            name: solutionDiscovery
            displayName: "Find all solutions"

  # 阶段2：动态加载自动生成的构建阶段
  - ${{ each stage in convertFromJson(variables['solutionDiscovery.buildStages']) }}:
      ${{ stage }}

如果不需要拆分阶段，可以直接在PowerShell中生成任务YAML，再通过convertFromYaml加载执行：

parameters:
  - name: SolutionPath
    type: string
    default: '$(System.DefaultWorkingDirectory)\Solutions'
  - name: SolutionFilter
    type: string
    default: "*.sln"
  - name: ContinueOnError
    type: boolean
    default: true
  - name: Clean
    type: boolean
    default: true

steps:
  # 自动发现解决方案并生成任务YAML
  - powershell: |
      # 提前安装powershell-yaml模块（首次运行需要）
      Install-Module -Name powershell-yaml -Force -Scope CurrentUser -SkipPublisherCheck
      
      $path = '${{ parameters.SolutionPath }}'
      $filter = "${{ parameters.SolutionFilter }}"
      $slnFiles = Get-ChildItem -Path $path -Filter $filter | Select-Object -ExpandProperty Name
      
      # 生成每个解决方案对应的任务组
      $tasks = @()
      foreach ($sln in $slnFiles) {
        # NuGet还原任务
        $restoreTask = @{
          task = "NuGetCommand@2"
          displayName = "Nuget restore $sln"
          inputs = @{
            command = "restore"
            restoreSolution = "Solutions/$sln"
            noCache = $true
          }
          continueOnError = ${{ parameters.ContinueOnError }}
        }
        
        # VSBuild构建任务
        $buildTask = @{
          task = "VSBuild@1"
          displayName = "Build $sln"
          inputs = @{
            solution = "Solutions/$sln"
            clean = $true
            restoreNugetPackages = $true
          }
          continueOnError = ${{ parameters.ContinueOnError }}
        }
        
        # Git清理任务
        $cleanTask = @{
          task = "PowerShell@2"
          condition = "and(succeeded(), eq('${{ parameters.Clean }}', 'True'))"
          displayName = "Git clean -xdf after $sln"
          inputs = @{
            targetType = "inline"
            script = "git clean -xdf"
          }
          continueOnError = ${{ parameters.ContinueOnError }}
        }
        
        $tasks += $restoreTask
        $tasks += $buildTask
        $tasks += $cleanTask
      }
      
      # 转换为YAML字符串并输出为变量
      $tasksYaml = $tasks | ConvertTo-Yaml -Depth 10
      Write-Host "##vso[task.setvariable variable=buildTasks;isOutput=true]$tasksYaml"
    name: solutionDiscovery
    displayName: "Find all solutions"

  # 动态加载生成的任务
  - ${{ each task in convertFromYaml(variables['solutionDiscovery.buildTasks']) }}:
      ${{ task }}

• 编译时表达式与运行时变量完全分离，不能用${{ each }}直接遍历运行时生成的变量。
• 方案1支持并行构建（去掉阶段的依赖关系即可），适合大型单体仓库；方案2更紧凑，适合小型流水线。

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