TeamCity - GitVersion generates the build number unexpected

user_4794611 0
Viewed 197

I have the git commits and the tags as below

enter image description here

The tag of the latest commit is 12.0.0-beta.6. When I run GitVersion, the result is as below

enter image description here

So the build number on TeamCity should be 12.0.0-beta.6, but I don't know why the GitVersion generates build number 12.0.0-beta.6+8 on TeamCity.

enter image description here

My build steps are as below

enter image description here enter image description here

Does anyone know why GitVersion generates the redundant "+8" after the FullSemVer? How to remove this dedundant "+8"? Thank you very much.

gitversion teamcity
2 Answers

The +8 is metadata and not actually part of the version number. In the documentation for the version variables, BuildMetaData is described as:

The build metadata, usually representing number of commits since the VersionSourceSha.

You can see the same value 8 exposed as CommitsSinceVersionSouce and this should increase with every commit made to the branch since its "version source", which in this case is the tag 12.0.0-beta.6 made on commit 549a1d.

The metadata does not increase with every build, but with every commit. I can see how the current language is confusing and the name BuildMetaData does not help. Since BuildMetaData is an exposed variable, we can't change its name, but I've submitted a PR that will hopefully clarify its documentation.

user_618180

Read carefully and understand at least part of GitVerson docs (paragraphs 1+2)

The shortest possible extraction

GitVersion will increment the metadata for each build so you can tell builds apart. For example, 1.0.0+5 followed by 1.0.0+6. It is important to note that build metadata is not part of the semantic version; it is just metadata!

user_9605580
Related