-
Notifications
You must be signed in to change notification settings - Fork 417
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
Local build fails when executing GitVersion #1548
Comments
cc gitversion experts @gep13 @david-driscoll @mholo65 |
The GitVersion task should not run locally, see: How are you executing the build? |
|
@wheelerlaw You seem to have gotten a little further than the rest of us in #1150 What version of |
I’m not sure what you mean, that PR is from over a year ago. And whatever version is included with .NET Core 3.whatever. I’ll find the exact version number when I’m next to my computer. |
@wheelerlaw Haha! Sorry, I made a typo, I meant to say #1500. |
The same situation on Windows 10: "GitVersion: Process returned an error (exit code 1)." |
@mholo65 Any ideas based on my last comment? I updated my original post to reflect the complete log. Just tried specifying the configuration as |
Okay, this appears to be an error within libgit2/libgit2sharp.nativebinaries Steps I took to workaround this bug:
So could this (the original issue, not the above download error) perhaps indicate that GitVersion is not using a new enough version of libgit2sharp.nativebinaries, and that the fix is simply updating it? (@asbjornu) |
jfc, so https://dotnetcli.azureedge.net/dotnet/Runtime/1.1.2/dotnet-runtime-1.1.2-linux-x64.tar.gz isn't even a valid link lol, awesome. It appears that line 734 in dotnet-installer is not creating the correct legacy link for Fedora: legacy_download_link="$(construct_legacy_download_link "$azure_feed" "$channel" "$normalized_architecture" "$specific_version")" || valid_legacy_download_link=false But that link gets created correctly in the Azure builds because the the Azure builds report being able to download the legacy version:
And the rabbit hole gets deeper... |
Okay, so it looks like it's because there's no explicit support for |
I had this problem when running ".\build.ps1" from a "detached head state". Just make sure you are in a proper branch. |
I was going to take a stab at fixing dotnet/vscode-csharp#3160, but I ran into some issues getting omnisharp to build locally.
I installed mono from their repository. I'm running Fedora 29
Here is the concatenated output:
Full output:
I am going to try to downgrade the
GitVersion
package to see if that will fix it, otherwise I'm pretty new with C#/mono build fundamentals so I'm at a loss at where to go from here.The text was updated successfully, but these errors were encountered: