Release 0.9.5 broke existing gitversion tasks
See original GitHub issueRelated to https://github.com/GitTools/GitVersion/issues/2434
Arguments that were happy running on 0.9.4 are now broken on 0.9.5:
Starting: GitVersion Config
==============================================================================
Task : Execute GitVersion Task
Description : Easy Semantic Versioning (http://semver.org) for projects using Git
Version : 0.9.4
Author : GitTools Contributors
Help : See the [documentation](https://gitversion.net/docs/) for help
==============================================================================
Command: dotnet-gitversion C:/agent/_work/46/s /output json /output buildserver /config C:\agent\_work\46\s\Templates\ComponentVersioning\GitVersion.yml /targetpath C:\agent\_work\46\s\Source /showconfig
C:\agent\_work\_tool\GitVersion.Tool\5.3.7\x64\dotnet-gitversion.exe C:/agent/_work/46/s /output json /output buildserver /config C:\agent\_work\46\s\Templates\ComponentVersioning\GitVersion.yml /targetpath C:\agent\_work\46\s\Source /showconfig
INFO [10/23/20 12:11:21:12] Working directory: C:\agent\_work\46\s\Source
assembly-versioning-scheme: Major
now:
Starting: GitVersion Config
==============================================================================
Task : Execute GitVersion Task
Description : Easy Semantic Versioning (http://semver.org) for projects using Git
Version : 0.9.5
Author : GitTools Contributors
Help : See the [documentation](https://gitversion.net/docs/) for help
==============================================================================
Command: dotnet-gitversion C:/agent/_work/46/s /output json /output buildserver /config C:\agent\_work\46\s\Templates\ComponentVersioning\GitVersion.yml /targetpath C:\agent\_work\46\s\Source /showconfig
C:\agent\_work\_tool\GitVersion.Tool\5.5.0\x64\dotnet-gitversion.exe C:/agent/_work/46/s /output json /output buildserver /config C:\agent\_work\46\s\Templates\ComponentVersioning\GitVersion.yml "/targetpath C:\agent\_work\46\s\Source /showconfig"
Unhandled Exception: GitVersion.WarningException: Could not parse command line parameter '/targetpath C:\agent\_work\46\s\Source /showconfig'.
at GitVersion.ArgumentParser.ParseTargetPath(Arguments arguments, String name, String[] values, String value, Boolean parseEnded) in D:\a\GitVersion\GitVersion\src\GitVersionExe\ArgumentParser.cs:line 194
at GitVersion.ArgumentParser.ParseSwitchArguments(Arguments arguments, NameValueCollection switchesAndValues, Int32 i) in D:\a\GitVersion\GitVersion\src\GitVersionExe\ArgumentParser.cs:line 126
at GitVersion.ArgumentParser.ParseArguments(String[] commandLineArguments) in D:\a\GitVersion\GitVersion\src\GitVersionExe\ArgumentParser.cs:line 88
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:15 (4 by maintainers)
Top Results From Across the Web
GitTools/GitVersion - Gitter
I have recently replaced a custom GitVersion script using 5.1.2 that ran in Azure Devops with the official GitVersion task on version 5.3.7....
Read more >GitVersion does not ignore commits before on DevOps
I added the ignore-commits-before tag to force version numbers to reset from 0.1.0. This works fine in local with gitversion (v. 5.8.1) ...
Read more >Documentation - GitVersion
GitVersion is a tool that generates a Semantic Version number based on your Git history. The version number generated from GitVersion can then...
Read more >GitTools - Visual Studio Marketplace
NuGetVersion) and $(GitVersion.SemVer) . It is also very configurable to allow it to work with most release workflows! Azure Pipelines tasks.
Read more >Buildbot 0.9.5 documentation
The default configuration allows everyone to perform any task like creating or stopping ... The current version of the Buildbot is additionally targeted...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@arturcic I have created PR #249
This workaround seems to work only for the YAML pipelines. I could not find a way to specify the version in the classic pipeline.
The problem from with those additional quotes was fixed with the previous 0.94 release, see bug #136 and PR #145