Azure DevOps YAML中如何用运行时变量动态加载环境模板？

核心矛盾在于：Azure DevOps的模板引用是编译时解析，而队列时间设置的$(environmentName)是运行时变量，编译阶段无法获取其实际值，导致直接引用模板路径失败。以下是两种可行的解决思路：

方法一：阶段级条件化加载模板 #

把环境模板的加载放到阶段的变量块中，通过运行时条件决定执行哪个环境的阶段，每个阶段对应一个环境模板，复用同一个作业模板。

示例代码 #

主管道YAML：

name: pipelineName_$(environmentName)_$(date:yyyyMMdd)
appendCommitMessageToRunName: false

trigger: none

variables:
- template: ../variables/release-pipeline-variables.yml

stages:
# 开发环境阶段
- stage: dev_stage
  displayName: Dev Environment Job
  condition: eq(variables['environmentName'], 'dev')
  variables:
  - template: ../variables/dev.yml
  jobs:
  - template: ../release-process-template.yml
    parameters:
      EnvironmentCode: ${{ variables.envCode }}
      EnvironmentName: 'dev'
      Pool: ${{ variables.testAgentPool}}
      Action: ${{ variables.action }}
      SomeId: ${{ variables.someId}}

# 测试环境阶段
- stage: stg_stage
  displayName: Stg Environment Job
  condition: eq(variables['environmentName'], 'stg')
  variables:
  - template: ../variables/stg.yml
  jobs:
  - template: ../release-process-template.yml
    parameters:
      EnvironmentCode: ${{ variables.envCode }}
      EnvironmentName: 'stg'
      Pool: ${{ variables.testAgentPool}}
      Action: ${{ variables.action }}
      SomeId: ${{ variables.someId}}

# 生产环境阶段
- stage: prd_stage
  displayName: Prd Environment Job
  condition: eq(variables['environmentName'], 'prd')
  variables:
  - template: ../variables/prd.yml
  jobs:
  - template: ../release-process-template.yml
    parameters:
      EnvironmentCode: ${{ variables.envCode }}
      EnvironmentName: 'prd'
      Pool: ${{ variables.testAgentPool}}
      Action: ${{ variables.action }}
      SomeId: ${{ variables.someId}}

这种方式保留了原有的环境模板结构，无需修改模板内容，通过运行时条件控制只执行对应环境的阶段。

方法二：运行时变量注入（脚本动态设置变量） #

先加载所有环境的变量到带前缀的变量中，再通过脚本根据$(environmentName)将对应环境的变量复制到全局变量，供后续作业使用。

步骤1：修改环境模板结构 #

将每个环境的变量添加对应前缀，示例dev.yml：

variables:
- name: dev_envCode
  value: dev
- name: dev_testAgentPool
  value: 'testAgentPool1'
- name: dev_ApiVersion
  value: 'dev1'
- name: dev_action 
  value: 'dev_action'
- name: dev_someId
  value: 'dev123'

同理修改stg.yml、prd.yml，前缀与环境名一致。

步骤2：主管道加载所有模板并添加脚本任务 #

name: pipelineName_$(environmentName)_$(date:yyyyMMdd)
appendCommitMessageToRunName: false

trigger: none

variables:
- template: ../variables/release-pipeline-variables.yml
- template: ../variables/dev.yml
- template: ../variables/stg.yml
- template: ../variables/prd.yml

stages:      
- stage: run_job
  displayName: Run job $(environmentName)
  dependsOn: []
  jobs:
  - job: set_env_vars
    displayName: Set Environment Variables
    pool:
      vmImage: 'ubuntu-latest'
    steps:
    - bash: |
        PREFIX=$(environmentName)
        # 复制对应环境的变量到全局
        echo "##vso[task.setvariable variable=envCode;isOutput=true]$${!PREFIX}_envCode"
        echo "##vso[task.setvariable variable=testAgentPool;isOutput=true]$${!PREFIX}_testAgentPool"
        echo "##vso[task.setvariable variable=ApiVersion;isOutput=true]$${!PREFIX}_ApiVersion"
        echo "##vso[task.setvariable variable=action;isOutput=true]$${!PREFIX}_action"
        echo "##vso[task.setvariable variable=someId;isOutput=true]$${!PREFIX}_someId"
      name: set_vars
      env:
        environmentName: $(environmentName)

  - job: run_release_process
    displayName: Run Release Process
    dependsOn: set_env_vars
    variables:
      envCode: $[ dependencies.set_env_vars.outputs['set_vars.envCode'] ]
      testAgentPool: $[ dependencies.set_env_vars.outputs['set_vars.testAgentPool'] ]
      ApiVersion: $[ dependencies.set_env_vars.outputs['set_vars.ApiVersion'] ]
      action: $[ dependencies.set_env_vars.outputs['set_vars.action'] ]
      someId: $[ dependencies.set_env_vars.outputs['set_vars.someId'] ]
    steps:
    - template: ../release-process-template.yml
      parameters:
        EnvironmentCode: $(envCode)
        EnvironmentName: $(environmentName)
        Pool: $(testAgentPool)
        Action: $(action)
        SomeId: $(someId)

这种方式只需一个阶段，适合环境较多的场景，但需要调整原有模板的变量命名规则。

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