-
Notifications
You must be signed in to change notification settings - Fork 654
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
[Improvement] Deprecate GitVersion.Commandline nuget package #3375
Comments
#3375 - stop publishing the GitVersion.Commandline nuget package
🎉 This issue has been resolved in version 6.0.0-beta.1 🎉 Your GitReleaseManager bot 📦🚀 |
I understand that this is the direction GitVersion is going, but this is a disappointing change. Previously, I could use NuGet to properly download and cache tooling reliably. It meant that any given build is not immediately subject to the whims of Internet package availability unless the package had actually changed. Now I have to either re-invent that caching myself or build my own NuGet package. The current alternatives all appear to be global tools, which are not suitable for CI environments, which in turn means a complicated dance of installing these onto something like Docker images. Was this really such a saving that the package had to be removed? |
Can you elaborate more on this? As far as I know the global tools install also in the same location as the regular nuget packages. |
It's possible I'm unaware of some aspect of global tools. With a NuGet package, I can control where the packages go with environment variables, and have multiple versions co-exist and be requested by version by tooling. With a global tool, I'm not sure how to achieve that; when last I tried, dotnet only worked properly when one version of a tool is present, which doesn't scale across hundreds of repos using different editions of toolings. |
Starting with version v6.0 we will deprecate the
GitVersion.Commandline
nuget package and the reasons are:GitVersion.Tool
if you have the dotnet sdk installedzip
files depending on the architecture you run on (you can find thezip
files as artifacts of every release)The text was updated successfully, but these errors were encountered: