-
Notifications
You must be signed in to change notification settings - Fork 656
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] LibGit2Sharp.LibGit2SharpException: this remote has never connected after updating to 5.10.0 #3082
Comments
Related issue #3081 |
I'm experiencing this as well currently - can the Edit: I probably should've looked first, it can be provided a version spec. Will try that for now until this is fixed. |
It is not clear to me that this is related to GitVersion. I saw an earlier pipeline run today that succeeded. I am using chocolatey to install GitVersion on the hosted build agent:
This pipeline failed: Initialize Job
Install GitVersion
Powershell script to invoke GitVersion and write out contents of Directory.Build.props file
This pipeline from earlier in the day succeeded: Initialize Job
Install GitVersion
Powershell script to invoke GitVersion and write out contents of Directory.Build.props file
|
So you think it may be the GitVersion setup task that is part of the Azure DevOps extension? Note that when I told the task to specifically install 5.9.0 all my pipelines started succeeding. Whenever it installed (or at least whenever it said it installed) 5.10.0 my pipelines failed. |
I also want to note that #1202 implies that this specific error is caused by a detached head. My pipelines in Azure DevOps running 5.9.0 are running against a PR branch and also have a detached head, and they are succeeding - so that doesn't appear to be the difference between these two scenarios. |
Switching to using version 5.9.0 does allow the pipeline to run. The yaml now includes:
But that still doesn't explain why earlier on today the pipeline ran without issue when using GitVersion 5.10.0. |
@asparrowhawk Did your successful run by chance run against a branch instead of a PR? Comments in #3081 imply that this issue is specific to when GitVersion is executed against a PR. |
Running into the same issue on Azure DevOps using version |
@orionstudt Success and failure of GitVersion today were seen on a PR. Yesterday's build of the main branch used GitVersion 5.10.0 and that ran without problem.
|
I would recommend to pin the version number always to avoid this type of 'surprises'. So for now I would recommend to pin to version 5.9.0 and when we find some time/will have more details, we will fix this issue. |
We experienced the same error in our AzDo pipelines. Downgrading to 5.9.0 resolves the problem, but that will require an update to many repositories. Can I suggest unlisting 5.10.0 until the issue is resolved? |
closed this in #3085 |
🎉 This issue has been resolved in version 5.10.1 🎉 Your GitReleaseManager bot 📦🚀 |
@IBlackI @cal5barton @asparrowhawk @FuncLun @orionstudt please confirm it's working for you with version 5.10.1 |
@arturcic Confirmed working with 5.10.1 |
@IBlackI thank you for quick confirmation |
@arturcic Also confirming 5.10.1 works Thank you for the quick action! |
@arturcic Yes, the new version is also working for me. |
Describe the bug
Gitversion execute throws a LibGit2Sharp.LibGit2SharpException after updating to version 5.10.0
Expected Behavior
GitVersion should be able to determine the correct version as when it was running 5.9.0
Logs have been stripped of sensitive information, and shortened.
Logs with 5.9.0:
Actual Behavior
Logs have been stripped of sensitive information, and shortened.
Logs with 5.10.0
Steps to Reproduce
Install 5.10.0 instead of 5.9.0.
Run gitversion/execute@0 task
Context
Builds fail on the gitversion/execute@0 task when the gitversion/setup@0 task installs 5.10.0.
Your Environment
Issue occurs on azure pipelines running the windows-2022 (windows-latest) image. The repository is hosted on the Azure DevOps Repos
The text was updated successfully, but these errors were encountered: