-
Notifications
You must be signed in to change notification settings - Fork 650
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] Mainline mode breaking change between 5.1.2 & 5.1.3 #2241
Comments
Seems like there are many problems related to tagged builds, lately. Any ideas what the source of those problems may be, @arturcic? I had an impression that our tests around this were pretty solid? |
I will try to find some time to look at |
Here are the diags on my local machine, if this can help you. For the 5.1.2 version :
For the 5.1.3 version :
|
On our Jenkins CI, we are building on merged branch (from source branch). For the 5.2.4 version on Jenkins :
|
I think this commit is the cause, at least this is the only one that makes sense 495ba8a |
Thanks for the investigation, @arturcic. I suppose these are the problematic lines of code?
If I'm not mistaken, this is how those lines of code looked before #1743 was merged:
In that case, we need to figure out why |
yes, would be handy to have some tests to cover that |
Indeed, that piece of logic right there is a prime candidate for some rigid unit tests. |
Any idea what the status on this is? Our builds still generate numbers with +1 (5.6.2 tag generates 5.6.3 builds) |
Sorry, but I don't think there's any news to report, @jackjwilliams. Unless we receive a pull request fixing this, I doubt it will be fixed. I'm not using |
Ok, I will try to dedicate some time this weekend to look at it. |
Is this problem still existing with version 6.0.0-beta.1? Could you please provide steps to reproduce? |
A lot of work has been done and it's not clear for me if this issue persists. I'm going to close it because there are no steps to reproduce. Please use the latest pre-release version and verify your scenario again... it might be solved. If not please re-open this issue or create a new bug. Thank you very much. |
Describe the bug
Breaking change in the version calculation on a tagged commit. The last working release is 5.1.2
Expected Behavior
Actual Behavior
Both outputs are the
dotnet gitversion
call on the exact same commit, with just differentGitVersion.Tool
versionsSteps to Reproduce
Build a tag on Jenkins with 5.1.3, with the following Gitversion.yml
Context
This bug breaks our release pipeline
Your Environment
Windows / Jenkins / dotnet core libs
Unfortunately, this happens on private projects, so can't link you to the git repo / CI
The text was updated successfully, but these errors were encountered: