You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched issues to ensure it has not already been reported
GitVersion package
AzureDevops task
What are you seeing?
I am using Gitversion tasks in Azure Release pipeline to find the next tag sequence. I have added update-build-number=false in the execute gitversion task.
Screenshot of the task attached
However, the release pipeline fails with the error:
2025-02-06T11:57:18.5806353Z Command: /opt/hostedtoolcache/GitVersion.Tool/6.0.5/dotnet-gitversion --roll-forward Major /home/vsts/work/r1/a/_temp/ /output json /l console /overrideconfig update-build-number=false
2025-02-06T11:57:21.7120908Z ##[error]Unable to process command '##vso[build.updatebuildnumber]0.3.0-alpha.0' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)
2025-02-06T11:57:21.7137378Z ##[error]Value cannot be null. (Parameter 'buildId')
Here are the version details of the task that I am using in the release pipeline
Prerequisites
GitVersion package
AzureDevops task
What are you seeing?
I am using Gitversion tasks in Azure Release pipeline to find the next tag sequence. I have added update-build-number=false in the execute gitversion task.
Screenshot of the task attached
However, the release pipeline fails with the error:
Here are the version details of the task that I am using in the release pipeline
steps:
Here is the link to stackoverflow discussion for detailed discussion - https://stackoverflow.com/questions/79417856/azure-devops-release-pipeline-throws-error-on-gitversion-updatebuildnumber
What is expected?
The Gitversion task in the release pipeline shouldn't attempt to update the build number
Steps to Reproduce
Create a Release pipeline in Azure with the following Tasks
Run the pipeline
Output log or link to your CI build (if appropriate).
The text was updated successfully, but these errors were encountered: