-
Notifications
You must be signed in to change notification settings - Fork 653
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] ref '.....' doesn't match the destination #3465
Comments
I think you have found a bug. For me it's not clear why this error occurred and also I cannot try/reproduce it because I'm not using Jenkins. Thus I need your help finding the root cause. Could you give me the hole exception stack trace please? Maybe this change is a candidate: #3459 |
Hi,
Let me know if you need other logs! |
Is it possible to provide a git repository or any steps to reproduce the problem? What version have you used before GitVersion 6.0.0-beta2? Could you provide the logs for the succesfull run please? Does this problem happen with GitVersion 6.0.0-beta1? |
Hi HHobek, |
Hi @HHobeck |
Hi @HHobeck |
First of all thank you for creating the test environment. Actually I'm quite busy at this moment and have no time to take a look into your issue. It's also related to infrastructure which I'm not familiar with. @arturcic Do you have time to take a look? |
I don't think the following month i will be able to spend time on this |
Ok, don't worry. I'm going to shutdown the test enviroment due the costs of infrastructure. When you able to check this issue, if you need the enviroment let me know, so I can restart it again. |
Hi, any news about this issue? |
I'm having the same problem, tested on 5.10.0, 5.11.0. and 5.12.0. As described above every build the problem from the previous build is resolved and the error is on the next update, e.g. 12:30:16 WARNING: INFO [06/27/23 12:30:14:97] Updating local branch release/2.4.2 to match ref release/2.4.2 16:33:39 WARNING: INFO [06/27/23 16:33:38:12] Updating local branch release/2.4.2 to match ref release/2.4.2 16:46:55 WARNING: INFO [06/27/23 16:46:53:80] Updating local branch release/2.4.2 to match ref release/2.4.2 full stack trace of the first instance (this was running 5.10.0): |
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. |
Sad to see that this issue is still open :( |
@mwijns, can you please test with the latest v6 beta?
@DanieleSky, we need a way to reproduce this. Did you manage to create a stable reproduction of the problem that we can have a look at? |
Are you able to share it publicly, or with me at [email protected]? |
@asbjornu I send you an email! |
Hi, do we have any information on this issue? |
No new information.. |
@DanieleSky Did you find a workaround ? |
@JohnyBro no.. today I tried to debug the issue but without success. |
Sorry for not finding time to debug this issue. All work on GitVersion is voluntary and unpaid, so we do it all on our free time. Finding the time and energy to debug a problem like this is therefore difficult. If anyone were able to reproduce the bug in an integration test, it would make the bug incredibly much simpler to fix. |
At the end I switched from Jenkins to GitLab (on prem) and all is working more or less as expected! |
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. |
This issue was closed because it has been stalled for 30 days with no activity. Thank you for your contributions |
Describe the bug
Hi, I'm using GitVersion 6.0.0-beta2 with Jenkins with Multibranch pipeline.
I'm using the standard configuration (I haven't GitVersion.yaml)
When I tag a commit and build it, GitVersion throw an error like this:
If I rerun the build the error change based of the name of all branch I have in the repository.
Like this:
LibGit2Sharp.LibGit2SharpException: ref 'refs/remotes/origin/main' doesn't match the destination
LibGit2Sharp.LibGit2SharpException: ref 'refs/remotes/origin/staging' doesn't match the destination
LibGit2Sharp.LibGit2SharpException: ref 'refs/remotes/origin/features-1' doesn't match the destination
After last branch the build works as expected:
Attach the configuration of Jenkins
Why the software have this behaviour?
There are some configurations that is wrong?
The text was updated successfully, but these errors were encountered: