Azure Pipelines中能否为仓库资源配置分支不存在时的备用引用？

问题 #

当前流水线运行正常，会针对所有仓库的release/*分支触发，符合需求。现在希望实现：当触发构建的分支（Build.SourceBranch）在某个或多个仓库中不存在时，自动使用备用引用（比如MASTER分支）。

当前流水线配置如下：

trigger:
- none

pool:
  name: <POOL_NAME>
  demands:
  - agent.name -equals  <AGENT_NAME>
# Overrides the value for Build.BuildNumber, which is used to name the artifact (ZIP file) that is produced

name: '$(Date:yyyyMMdd)T$(Hours)$(Minutes)$(Seconds)'

resources:
  repositories:
  - repository: REPO-A
    type: git
    ref: $(Build.SourceBranch)
    name: <COMPANY>/REPO-A
    trigger:
      branches:
        include:
        - 'release/*'

  - repository: REPO-B
    type: git
    ref: $(Build.SourceBranch)
    name: <COMPANY>/REPO-B
    trigger:
      branches:
        include:
        - 'release/*'
          
stages:
- stage: 'BuildAndUploadArtifact'
  jobs:
  - job:
    workspace:
      clean: all
    steps:
    - checkout: self
    - checkout: REPO-A
    - checkout: REPO-B

    - task: CmdLine@2
      inputs:
        script: |
          echo "hello, world!"

场景说明 #

• 场景1（正常运行）：REPO-A和REPO-B均存在release/2024-1和release/2024-2分支。当在REPO-A的release/2024-1分支提交代码时，两个仓库都会检出release/2024-1分支，流水线正常执行。
• 场景2（执行失败）：REPO-A存在release/2024-1分支，而REPO-B仅存在MASTER分支。此时触发流水线会因REPO-B找不到对应分支而失败。

需求：为REPO-B指定备用分支（如MASTER），让REPO-A用触发分支，REPO-B在分支不存在时自动用备用分支，请问能否实现？

注意：实际场景包含更多仓库，后续会将这些仓库一起构建为一个应用。

解决方案 #

可以实现这个需求，核心思路是不直接在resources.repositories中硬编码ref，而是通过脚本动态检测目标分支是否存在，再执行对应的检出逻辑。具体步骤如下：

1. 修改流水线配置，移除固定分支引用 #

先把resources中的仓库配置去掉固定ref，避免流水线提前校验分支存在性：

trigger:
- none

pool:
  name: <POOL_NAME>
  demands:
  - agent.name -equals  <AGENT_NAME>

name: '$(Date:yyyyMMdd)T$(Hours)$(Minutes)$(Seconds)'

resources:
  repositories:
  - repository: REPO-A
    type: git
    name: <COMPANY>/REPO-A
    trigger:
      branches:
        include:
        - 'release/*'

  - repository: REPO-B
    type: git
    name: <COMPANY>/REPO-B
    trigger:
      branches:
        include:
        - 'release/*'
          
stages:
- stage: 'BuildAndUploadArtifact'
  jobs:
  - job:
    workspace:
      clean: all
    steps:
    - checkout: self
      persistCredentials: true # 保留凭据，用于后续git操作

    # 动态处理REPO-A的检出（沿用触发分支，无备用需求可直接检出）
    - task: CmdLine@2
      displayName: 'Checkout REPO-A'
      inputs:
        script: |
          git clone -b $(Build.SourceBranchName) https://dev.azure.com/<COMPANY>/<PROJECT>/_git/REPO-A $(Build.SourcesDirectory)/REPO-A

    # 动态处理REPO-B的检出，指定MASTER为备用分支
    - task: CmdLine@2
      displayName: 'Checkout REPO-B with fallback to MASTER'
      inputs:
        script: |
          TARGET_BRANCH=$(Build.SourceBranchName)
          FALLBACK_BRANCH='MASTER'

          # 查询远程仓库是否存在目标分支
          git ls-remote --heads https://dev.azure.com/<COMPANY>/<PROJECT>/_git/REPO-B refs/heads/$TARGET_BRANCH
          if [ $? -eq 0 ]; then
            echo "找到目标分支$TARGET_BRANCH，开始检出"
            git clone -b $TARGET_BRANCH https://dev.azure.com/<COMPANY>/<PROJECT>/_git/REPO-B $(Build.SourcesDirectory)/REPO-B
          else
            echo "未找到目标分支$TARGET_BRANCH，切换至备用分支$FALLBACK_BRANCH"
            git clone -b $FALLBACK_BRANCH https://dev.azure.com/<COMPANY>/<PROJECT>/_git/REPO-B $(Build.SourcesDirectory)/REPO-B
          fi

    - task: CmdLine@2
      inputs:
        script: |
          echo "hello, world!"

2. 关键细节说明 #

• persistCredentials: true：开启后流水线会保留Azure DevOps凭据，避免git clone时需要手动验证身份。
• git ls-remote：无需克隆仓库即可远程查询分支是否存在，效率更高。
• 批量适配：如果有大量仓库，可以将检出逻辑封装成通用脚本，通过参数传递仓库名、目标分支、备用分支，减少重复代码。
• 灵活调整备用分支：每个仓库可以单独设置不同的备用分支，比如部分仓库用基础release分支，部分用MASTER，满足差异化需求。

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