-
Notifications
You must be signed in to change notification settings - Fork 652
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
[Bug] 5.5.1 Continue failing to get version when building from tag #2456
Comments
I'm also getting this. Downgrading until this is fixed. |
I've managed to get a workaround for this problem modifying the regex used for release configuration:
Now GitVersion is calculating version accordly:
|
I had this problem on 5.3, then reverted to 5.1.2. Now I migrated to 5.6.0 and it seems to be solved for us. This is our config:
|
@brechtvhb thank you for the feedback. @farlop any feedback from you? |
Please find below a re-run of a build from a tag using GitVersion 5.6.0. It seems it's still not able to find out that I'm building from a tag in Azure DevOps server. (build number 1.1.0-tags-1-0-4.1+15 instead of 1.0.4)
|
I just had this usse too :(
|
Will rebase with proper commit message and tests later.
Will rebase with proper commit message and tests later.
Without the code change, this test fails with an incorrectly asserted version number, similar to 0.3.0-tags-01, when it should be 0.2.0.
Ensure that an increment of the version number only occurs when the sha of the commit is different from the base version sha.
Without the code change, this test fails with an incorrectly asserted version number, similar to 0.3.0-tags-01, when it should be 0.2.0.
Without the code change, this test fails with an incorrectly asserted version number, similar to 0.3.0-tags-01, when it should be 0.2.0.
Since this is where the original issue was reported.
Ensure that an increment of the version number only occurs when the sha of the commit is different from the base version sha.
Without the code change, this test fails with an incorrectly asserted version number, similar to 0.3.0-tags-01, when it should be 0.2.0.
Since this is where the original issue was reported.
Describe the bug
As fix for bug #2074 was released in v5.5.1, I've checked that maybe I'm running in a different scenario:
We are using TrunkBasedDevelopment (TBD) with a configuration file like:
Expected Behavior
The build for a tagged commit shoud be calculated as 1.0.4
Actual Behavior
The build number is being calculated as 1.1.0-tags-1-0-4.1+15
As GitVersion creates a new branch named 'tags/1.0.4' it fails calculating the version.
Steps to Reproduce
When we add a new fix we proceed as follow:
You can reproduce it with dotnet gitversion tool:
Your Environment
We are using Azure DevOps Server 2019
The text was updated successfully, but these errors were encountered: