gittools

I have a couple of webapps I am adding gitversion to. Main problem - GitVersion is generating a MajorMinorPatchTag where the Major is in the format yyyymmdd. Aside from this not being a valid major version, I want the usual versioning 0.1.3.alpha.1 in the example below but I am getting 20201021.1.1.

I have removed all the old build tags from the repo so it does not appear to be finding this from tags. Is there anywhere else I can force it to ignore previous build versions and use the semver starting from the gitversion.yml/next-version setting?

Detail below:

The gitversion.yml is simple:

I'm hoping to use fuzzy wuzzy to compare all strings in a list against each other, but it looks not every string is being compared against one another in the list. Here's what I've tried:

I'm trying to install package in julia 1.4.2 but it always returns this:

I can successfully get the full json string with:

I have a Visual Studio project which is built as a NuGet lib package. But every time I publish the package, I have to change the version number manually. That's a prone-to-error work. I'd like to generate and increase the package version number automatically.

I found GitVersion tool to solve this problem. And I also found some semantic versioning blogs to explain the package version of continuous delivery.

• GitTools/GitVersion: Easy Semantic Versioning (http://semver.org) for projects using Git
• GitVersion Documentation
• Versioning NuGet packages in a continuous delivery world: part 1 – Microsoft DevOps Blog
• Versioning NuGet packages in a continuous delivery world: part 2 – Microsoft DevOps Blog
• Versioning NuGet packages in a continuous delivery world: part 3 – Microsoft DevOps Blog

But unfortunately, The GitVersion package does not work correctly for me.

• It gives me an error that AssemblyVersionAttribute is duplicated.
• If I add false into the csproj file, It will do nothing and the package version will be 0.0.0.0.

Maybe the reason is that I'm using the new csproj format. See here to view the csproj file and the file looks like this:

Talking about UseGitVersion@5 Azure DevOps task, which is a wrapper around the actual GitVersion tool. I looked at the various GitVersion configuration options, but I could not find anything that will increment per build. Not per commit, per build. I have a build counter value I can pass to GitVersion, if it would be willing to accept it somehow, but I don't see any argument or option to use it.

The only option I found so far is to override the next-version value in GitVersion.yml, but I would prefer to increment the PreReleaseTag rather than the semver.

I tried

I've an ASP.NET Core application I'm publishing on a dedicated server via Azure DevOps build/release pipelines.

I'm managing the application version number with the GitVersion task (gittools.gitversion.gitversion-task.GitVersion@4) in the YAML build.

The build step is something like:

I have this in my gitlab-ci.yml: