如何在Azure DevOps合并Pull Request时自动创建Git标签？

一、直接报错原因：路径变量拼写错误 #

你在PublishBuildArtifacts@1任务中使用了错误的变量名：$(Build.ArtifacStagingDirectory)，正确的变量名应为$(Build.ArtifactStagingDirectory)（缺少字母t），这是触发No files matched the search pattern报错的直接原因。

二、PR触发逻辑修正 #

当前流水线仅监听main分支的提交，无法在PR完成时自动触发构建。需添加PR触发器，覆盖dev/qa/main分支的PR完成事件：

trigger:
- main
- dev
- qa

pr:
  branches:
    include:
    - main
    - dev
    - qa
  autoCancel: false

三、Checkout步骤优化 #

流水线默认会自动执行checkout: self，无需重复添加。若需要持久化凭证，应在默认的checkout步骤中配置：

steps:
  - checkout: self
    persistCredentials: true  # 开启凭证持久化，用于Git标签推送
    fetchDepth: 0  # 拉取完整仓库历史，避免标签推送时的分支信息缺失

四、Git标签推送逻辑修正 #

调整Git配置与标签命名规则，确保仅在PR触发的构建中执行标签推送：

- script: |
    git config user.email "tunombre@ejemplo.com"
    git config user.name "Tu Nombre"
    # 用PR ID+构建ID命名标签，关联PR与版本
    TAG_NAME="pr_release_$(System.PullRequest.PullRequestId)_$(Build.BuildId)"
    git tag $TAG_NAME
    git push origin $TAG_NAME
  displayName: 'Crear y empujar tag de Git'
  condition: ne(variables['System.PullRequest.PullRequestId'], '')  # 仅PR触发时执行

五、完整修正后的流水线配置 #

整合所有修复后的完整pipeline.yml：

trigger:
- main
- dev
- qa

pr:
  branches:
    include:
    - main
    - dev
    - qa
  autoCancel: false

pool:
  vmImage: ubuntu-latest

steps:
  - checkout: self
    persistCredentials: true
    fetchDepth: 0

  - task: UseDotNet@2
    displayName: 'Install SDK .Net'
    inputs:
      version: 7.x
      performMultiLevelLookup: true

  - task: DotNetCoreCLI@2
    displayName: 'Restore APP'
    inputs:
      command: 'restore'
      projects: '**/ProyectoUno.csproj'
      feedsToUse: 'select'
      vstsFeed: '2822941f-fa33-4f11-8dd5-0a4d3a7657c6'

  - task: DotNetCoreCLI@2
    displayName: 'Build APP'
    inputs:
      command: 'build'
      projects: 'ProyectoUno/*.csproj'
      arguments: '--no-restore --configuration $(BuildConfiguration)'

  - task: DotNetCoreCLI@2
    displayName: 'Publish APP'
    inputs:
      command: 'publish'
      publishWebProjects: false
      projects: 'ProyectoUno/*.csproj'
      arguments: '--no-restore --configuration $(BuildConfiguration) --output "$(Build.ArtifactStagingDirectory)"'

  - script: |
      git config user.email "tunombre@ejemplo.com"
      git config user.name "Tu Nombre"
      TAG_NAME="pr_release_$(System.PullRequest.PullRequestId)_$(Build.BuildId)"
      git tag $TAG_NAME
      git push origin $TAG_NAME
    displayName: 'Crear y empujar tag de Git'
    condition: ne(variables['System.PullRequest.PullRequestId'], '')

  - task: PublishBuildArtifacts@1
    inputs:
      PathtoPublish: '$(Build.ArtifactStagingDirectory)'
      ArtifactName: 'ProyectoUno'
      publishLocation: 'Container'

额外注意事项 #

• 确保流水线服务账号（Project Collection Build Service）拥有仓库的Contribute权限，否则无法推送标签
• 标签命名加入PR ID可清晰关联每个PR对应的版本，避免标签冲突
• condition配置确保标签仅在PR触发的构建中执行，避免普通分支提交重复打标签

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