Azure DevOps构建流水线打标签成功但日志报错求助

I’ve run into this exact scenario before—your tag gets pushed successfully but the pipeline logs throw an [error] flag anyway. Let’s break down what’s happening and how to fix it:

What’s Causing the False Error? #

Azure DevOps parses output from shell scripts strictly, and sometimes Git sends non-error messages to stderr (standard error stream) during operations like git push. Even though the tag was created and pushed correctly, the pipeline picks up those stderr lines and marks them as errors.

Solution 1: Redirect Git Output to Avoid False Errors #

Modify your script step to redirect stderr to stdout for the git push command. This ensures Azure DevOps doesn’t misinterpret Git’s verbose output as an error:

steps:
- checkout: 'self'
  clean: true
  persistCredentials: true
- script: |
    git tag Build_$(Build.BuildId)
    # Redirect stderr to stdout to prevent false error marking
    git push origin Build_$(Build.BuildId) 2>&1
  workingDirectory: $(Build.SourcesDirectory)

Solution 2: Use Azure DevOps’ Built-in Git Tag Task #

For a more reliable, pipeline-native approach, swap the script with Azure DevOps’ official GitTag task. This task is designed to handle Git operations cleanly without log parsing issues:

steps:
- checkout: 'self'
  clean: true
  persistCredentials: true
- task: GitTag@0
  inputs:
    tag: 'Build_$(Build.BuildId)'
    push: true
    repo: 'self'

Bonus: Debug to Confirm No Actual Errors #

If you want to verify there’s no real issue with the push, add debug logging to your script to see the full Git output:

- script: |
    # Enable debug output to see exactly what Git is doing
    set -x
    git tag Build_$(Build.BuildId)
    git push origin Build_$(Build.BuildId)
  workingDirectory: $(Build.SourcesDirectory)

Check the detailed logs—you’ll likely see the tag was pushed successfully, and the "error" was just a misinterpreted log line.

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