Skip to content

[Bug] GitVersion produces errors on TFS 2018 and older #3003

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
conmilo opened this issue Feb 18, 2022 · 3 comments
Closed

[Bug] GitVersion produces errors on TFS 2018 and older #3003

conmilo opened this issue Feb 18, 2022 · 3 comments
Labels

Comments

@conmilo
Copy link

conmilo commented Feb 18, 2022

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

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')

Environment

  • GitVersion 5.8.2+Branch.main.Sha.90dc2bedb08ac54498bddcc279cde5c4596a18d3
  • Team Foundation Server 2017 (15.117.26714.0)

Relevant Line of Code

$"##vso[task.setvariable variable=GitVersion.{name};isOutput=true]{value}"

Workaround

Select the Control Option "Continue on error"

@conmilo
Copy link
Author

conmilo commented Apr 4, 2022

Still applies to GitVersion 5.9.0. Anyone have any thoughts on this?

@github-actions
Copy link

github-actions bot commented Mar 4, 2023

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.

@github-actions github-actions bot added the stale label Mar 4, 2023
@github-actions
Copy link

github-actions bot commented Apr 4, 2023

This issue was closed because it has been stalled for 30 days with no activity. Thank you for your contributions

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant