Use convention to derive a SemVer product version from a GitFlow based repository
So I will try out according to your suggestion. Hope that gitVersion will look into root repository repo for the yml file, since the cake tool folder is in .gitignore
thanks for the help
I wonder one more thing, If I use continous delivery mode for non release branches to increase patch version. For which branch merges do the patch set increase?
Having issues with gitVersion taking long time to determine version, searching through all merge bases. Now testing on development branch. How to remedy this? Let's say e.g. development branch should only reference development branch or what is contained within the the master branch
For local builds it can then however still be slow. But enforcing a workflow to increment the version only in central CI environment, there could always be the approach of not executing gitVersion locally (on the entire repo)
Let's say using continous deployment mode over time and generating new versions, will it be slow when there is no gitTag to use as base for the version calculation after a while. Let's say that there are e.g. 300 commits without any gitTag. Increasing patch set on each one.
Noticing that the setting "tracks-release-branches:true" on development branch caused the search mayhem (taking 20 minutes instead of below 1 minute). Luckily we are not following GitFlow, so just to disable that. The behavior was noted on feature branch, branched of from development.
In versioning the head in my develop branch, gitversion is finding the previous commit as base, which is tagged, but returning that same version (doesnt increment anything), anyone have an idea why? diag looks like this: Base version used: Git tag 'v0.3.0-alpha-0001': 0.3.0-alpha-0001 with commit count source 62ac01da5c9805fcf101d534c07054dfc6040292 (Incremented: 0.3.0-alpha-0001)
Hello, I was looking at using GitVersion in a docker container. I don't see anything about docker in the docs and links of the tags in docker hub description are broken. Is it recommended to use, or not very used/supported? (https://hub.docker.com/r/gittools/gitversion)
We've just started using release/ branches as we are out of development mode and going to production. The first one was release/2.1.0. I asked everyone to branch off of this for fixes. So we use our normal fix/license-bug type branches. But GitVersion freaked out, saying it couldn't find the source branch. When I add a fix header to GitVersion.yml, with source-branches of release, it still builds 2.2.0-license-bug1, when I was expecting 2.1.0-license-bug2 (since it was branched from release/2.1.0. Am I doing this wrong?
Or is there a recommended branching strategy for bugfixes off of release/* branches?
GitVersion will calculate the next version for you. This is by design
If you would use GitTag as bearer of version information, the commit which has the actual gittag with version information will dhow that information as version. The following commit(s) will have the calculated next version
But why does it keep using develop when I have explicitly said source-branches: ['release'] ?
@/all Version 5.0.0 of the GitVersion has just been released, https://www.nuget.org/packages/GitVersion.Tool, https://github.com/GitTools/GitVersion/releases/tag/5.0.0
does this apply also to a Task ?
Its seems yes :) cool
Thank you everyone for your contribution!
specifically, Azure DevOps Pipelines
(using the "classic" editor; I haven't moved this to yaml yet)
I've been using GitVersion on this build for a while and it works great
recently, it seems to have changed how it's tagging the commits when the build is done
it used to come out in the format
2.1.1
now it comes out as
2.1.1+5
how do I get it to stop adding the suffix?
as far as I can tell from the docs, something like
$(GitVersion_NuGetVersionV2) should work, but if I use that as the option it prints that as a literal string
and yes, I've added
/output buildserver to the additional args
+5 is likely the revision number, each build needs to be unique, tried
$(GitVersion.NuGetVersion) mentioned at https://gitversion.readthedocs.io/en/latest/build-server-support/build-server/tfs-build-vnext/
I'm guessing though as I use Cake or MSBuild task myself.