GitVersion: [Bug] Build number in Azure DevOps wrong
Describe the bug The build number in Azure DevOps has changed and most likely not respecting my GitVersion.yml file anymore.
Expected Behavior
The build number should be 2.4.0-beta.24 when building off a tag called 2.4.0-beta.24.
Actual Behavior
The build number is set to 2.4.0-tags-2-4-0-beta-24.1 when building off of the tag 2.4.0-beta.24
Possible Fix
This seems to have been introduced in 5.12.0. If I revert back to 5.11.x, it works as it should. Could this somehow be related to the prerelease tag changes that were made? Is it because I don’t have a beta tag against the master branch in my config but I’m specifying it in a tag or something?
Here is the compare between the two versions for reference: https://github.com/GitTools/GitVersion/compare/5.11.1...5.12.0
Context
this is making a mess of my NuGet packages, as they are all now submitted with the weird version.
Your Environment
- Version Used: 5.12.0
- Operating System and version (Windows 10, Ubuntu 18.04): Azure DevOps, agent vmImage: ‘windows-latest’, .NET 6.0
My GitVersion.yml file:
assembly-versioning-scheme: Major
assembly-informational-format: '{Major}.{Minor}.{Patch}{PreReleaseTagWithDash}+{CommitsSinceVersionSource}.Branch.{EscapedBranchName}.Sha.{ShortSha}'
mode: ContinuousDelivery
increment: Inherit
#tag-prefix: '[vV]'
branches:
master:
regex: ^master
mode: ContinuousDelivery
tag: ''
increment: Patch
prevent-increment-of-merged-branch-version: true
track-merge-target: false
tracks-release-branches: false
is-release-branch: true
release:
regex: ^releases?[/-]
mode: ContinuousDelivery
tag: beta
increment: Patch
prevent-increment-of-merged-branch-version: true
track-merge-target: false
tracks-release-branches: false
is-release-branch: true
feature:
regex: ^features?[/-]
mode: ContinuousDeployment
tag: alpha
increment: Minor
prevent-increment-of-merged-branch-version: false
track-merge-target: false
tracks-release-branches: false
is-release-branch: false
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 3
- Comments: 19 (16 by maintainers)
Commits related to this issue
- Workaround for GitTools/GitVersion#3351 — committed to gerardog/gsudo by gerardog a year ago
Hi @HHobeck, thanks for your thorough explanation. I will have a shot at these suggestions and let you know if I 'm still stuck.
Regards,