Azure DevOps流水线中如何遍历对象减少容器推送重复代码？

一、直接使用数据模型数组（YAML原生支持） #

Azure DevOps YAML流水线完全支持定义包含多字段的结构化数据模型数组，无需额外依赖就能实现代码复用，后续扩展也只需新增数组条目。

示例实现：

variables:
  # 定义包含多字段的服务配置数组
  services: |
    [
      {"name": "user-service", "path": "./src/user-service", "imageName": "acr-registry.azurecr.io/user-service"},
      {"name": "order-service", "path": "./src/order-service", "imageName": "acr-registry.azurecr.io/order-service"},
      {"name": "payment-service", "path": "./src/payment-service", "imageName": "acr-registry.azurecr.io/payment-service"}
    ]

jobs:
- job: PushImages
  displayName: 推送容器镜像
  steps:
  # 遍历数组，为每个服务生成推送任务
  - ${{ each service in convertToJson(variables.services) }}:
    - task: Docker@2
      displayName: 构建并推送 ${{ service.name }} 镜像
      inputs:
        containerRegistry: 'ACR-Service-Connection'
        repository: ${{ service.imageName }}
        command: 'buildAndPush'
        Dockerfile: '${{ service.path }}/Dockerfile'
        tags: |
          $(Build.BuildId)
          latest

二、从外部JSON文件读取配置（分离配置与流水线代码） #

如果希望配置单独维护、不与流水线代码耦合，可以把服务配置存入仓库中的JSON文件，再通过脚本解析后传入流水线。

步骤1：创建配置文件 #

在代码仓库根目录新建service-configs.json：

[
  {"name": "user-service", "path": "./src/user-service", "imageName": "acr-registry.azurecr.io/user-service"},
  {"name": "order-service", "path": "./src/order-service", "imageName": "acr-registry.azurecr.io/order-service"},
  {"name": "payment-service", "path": "./src/payment-service", "imageName": "acr-registry.azurecr.io/payment-service"}
]

步骤2：流水线中读取并解析配置 #

用PowerShell解析JSON并生成流水线变量，再循环执行推送任务：

jobs:
- job: PushImages
  displayName: 推送容器镜像
  steps:
  - pwsh: |
      $configs = Get-Content ./service-configs.json | ConvertFrom-Json
      $serviceNames = @()
      foreach ($config in $configs) {
        # 为每个服务设置独立变量
        Write-Host "##vso[task.setvariable variable=services.$($config.name).path]$($config.path)"
        Write-Host "##vso[task.setvariable variable=services.$($config.name).imageName]$($config.imageName)"
        $serviceNames += $config.name
      }
      # 输出服务名称列表供后续循环使用
      Write-Host "##vso[task.setvariable variable=serviceNames;isOutput=true]$($serviceNames -join ',')"
    name: ReadConfigs
    displayName: 读取服务配置文件

  # 遍历服务名称列表，执行推送任务
  - ${{ each serviceName in split(variables['ReadConfigs.serviceNames'], ',') }}:
    - task: Docker@2
      displayName: 构建并推送 ${{ serviceName }} 镜像
      inputs:
        containerRegistry: 'ACR-Service-Connection'
        repository: ${{ variables['services.' + serviceName + '.imageName'] }}
        command: 'buildAndPush'
        Dockerfile: '${{ variables['services.' + serviceName + '.path'] }}/Dockerfile'
        tags: |
          $(Build.BuildId)
          latest

三、进阶：结合模板任务解耦逻辑 #

如果推送逻辑复杂，可将Docker推送步骤抽成独立模板文件，进一步降低维护成本：

模板文件docker-push-template.yml #

parameters:
- name: serviceName
  type: string
- name: servicePath
  type: string
- name: imageName
  type: string

steps:
- task: Docker@2
  displayName: 构建并推送 ${{ parameters.serviceName }} 镜像
  inputs:
    containerRegistry: 'ACR-Service-Connection'
    repository: ${{ parameters.imageName }}
    command: 'buildAndPush'
    Dockerfile: '${{ parameters.servicePath }}/Dockerfile'
    tags: |
      $(Build.BuildId)
      latest

主流水线引用模板 #

variables:
  services: |
    [
      {"name": "user-service", "path": "./src/user-service", "imageName": "acr-registry.azurecr.io/user-service"},
      {"name": "order-service", "path": "./src/order-service", "imageName": "acr-registry.azurecr.io/order-service"},
      {"name": "payment-service", "path": "./src/payment-service", "imageName": "acr-registry.azurecr.io/payment-service"}
    ]

jobs:
- job: PushImages
  displayName: 推送容器镜像
  steps:
  - ${{ each service in convertToJson(variables.services) }}:
    - template: docker-push-template.yml
      parameters:
        serviceName: ${{ service.name }}
        servicePath: ${{ service.path }}
        imageName: ${{ service.imageName }}

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