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
There is an issue calling GitVersion via command line on Azure DevOps Server (TFS) 2018 and older. Apparently these versions of TFS do not have the capability of setting output variables with the isOutput flag. See also #2426 and microsoft/azure-pipelines-agent#3284
Command line task calling dotnet gitversion /output buildserver /nofetch
Error Produced
Unable to process command '##vso[task.setvariable variable=GitVersion.Major;isOutput=true]0' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)
Value cannot be null. (Parameter 'RefName')
Unable to process command '##vso[task.setvariable variable=GitVersion.Minor;isOutput=true]1' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)
Value cannot be null. (Parameter 'RefName')
Unable to process command '##vso[task.setvariable variable=GitVersion.Patch;isOutput=true]0' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)
Value cannot be null. (Parameter 'RefName')
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
There is an issue calling GitVersion via command line on Azure DevOps Server (TFS) 2018 and older. Apparently these versions of TFS do not have the capability of setting output variables with the isOutput flag. See also #2426 and microsoft/azure-pipelines-agent#3284
Reproduction Steps
See Using GitVersion with the Command Line build step
Command line task calling
dotnet gitversion /output buildserver /nofetch
Error Produced
Environment
Relevant Line of Code
GitVersion/src/GitVersion.Core/BuildAgents/AzurePipelines.cs
Line 21 in 90dc2be
Workaround
Select the Control Option "Continue on error"
The text was updated successfully, but these errors were encountered: