-
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] 5.6.5 Does not recognise master as a source-branch #2587
Comments
We are facing similar error as reported by WesToleman, today we are unable to generate a build using Azure Devops, and its failing across different branches while calculating the newer version Version: GitVersion.Tool 5.6.5 x64 ERROR [02/08/21 4:51:07:31] An unexpected error occurred: ERROR [02/08/21 4:51:07:31] An unexpected error occurred: |
We are also facing the same issue, and 5.6.4 seems to be working. @sairamb87 you can update the pipeline step to use exact version until we have a fix. |
@lankaapura, Thank you 👍 Yes, 5.6.4 is working fine, and we have already updated our pipelines to use this version, until we get a fix for 5.6.5 |
I assume this is related to #2573. |
Yes, working on it |
Thanks @arturcic for getting it fixed fast 👍 when can we expect the new release/patch? |
🎉 This issue has been resolved in version 5.6.6 🎉 Your GitReleaseManager bot 📦🚀 |
Can you all confirm it is fixed? |
@arturcic Thanks for resolving this issue, 5.6.6 version is working as expected 👍 |
@sairamb87 thanks for the confirmation |
GitVersion 5.6.5 fails to calculate a version for our latest merge to master. "An unexpected error occurred: GitVersion.Configuration.ConfigurationException: Branch configuration 'breaking' defines these 'source-branches' that are not configured: '[master]'".
Expected Behavior
GitVersion calculates a new version for the latest merge to master.
Actual Behavior
It fails to generate a version.
Steps to Reproduce
Use this custom GitVersion configuration. Merge into master, attempt to calculate a new master version.
Context
Our master is always shippable so every merge must have a new release version. The custom configuration automatically generates a new version according to the prefix of the merged branch.
Your Environment
Using the GitVersion.CommandLine package on Windows. Fails on both CI Build on TeamCity and locally.
The text was updated successfully, but these errors were encountered: