-
Notifications
You must be signed in to change notification settings - Fork 534
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
[build] use WorkingDirectory for <GitBlame/> #2594
Conversation
Downstream in monodroid, I'm getting a build failure such as: /usr/bin/git blame "/full/path/to/external/xamarin-android/Configuration.props" XAVersionInfo.targets(53,5): error MSB6006: "git" exited with code 128. XAVersionInfo.targets(61,5): error MSB4044: The "GitCommitsInRange" task was not given a value for the required parameter "StartCommit". If I run the git command manually: fatal: not a git repository (or any of the parent directories): .git It seems we shouldn't be using a full path here, but use `WorkingDirectory` instead? Maybe it will not work if `xamarin-android` is a submodule? This has somehow been working in the past, so perhaps my version of git is the cause? $ git --version git version 2.17.1 (Apple Git-112)
Oh apparently someone else had this problem: #2574 |
Don't know what happened to the build...
I got the same error when I rebased: #2590 |
The current build failed because the machine had NDK r18 installed (because that build machine previously built PR #2592), and thus the build machine is now "corrupt". :-( We need to figure out support for NDK downgrades. |
build |
The problem isn't the full path (and we want the full path, just for sanity). The problem is that your git checkout is (partially) FUBAR. Unfortunately I can't readily find how to fix a FUBAR repo, short of nuking it and checking it out again. For example, a few weeks ago I moved my git checkout from one directory into another.
That's the new dir, not the old dir, but the problem is that it's a full path, so when I moved my git checkout, the path was invalidated, and every I had to find and manually edit each of these in order to get Regardless, using a full path should be perfectly valid, and if What we can do is improve the error message. What we currently generate is not helpful, because the actual We should fix that: surface the |
So I did a fresh checkout and I'm still having the problem with our private repo:
This failure:
But this command works fine:
That's why I'm wondering if we can set |
$ cd $HOME
$ git blame /path/to/Configuration.props (Unless When within a git repo, using a full path Works For Me™ $ cd /path/to/xamarin-android
$ git blame /path/to/xamarin-android/Configuration.props
# no error Discussing this on gitter, it could be a Which suggests that we should accept this PR, to decrease git version dependencies. |
build |
Downstream in monodroid, I'm getting a build failure such as:
If I run the git command manually:
It seems we shouldn't be using a full path here, but use
WorkingDirectory
instead? Maybe it will not work ifxamarin-android
is a submodule?This has somehow been working in the past, so perhaps my version of
git is the cause?