GitKraken with TFS 2017

Question

I have successfully used GitKraken with TFS 2015. But after upgrading to Tfs 2017, it cannot pull or push. If I use the https endpoint, it always tries to login to the server. If I use an SSH endpoint, it gives me an Early EOF exception.

Can someone help me if I need to configure something on TFS 2017 so Kraken can use this endpoint? How can I find out what is the problem with the SSH endpoint? I can not find anything related in the magazines.

Or is GitKraken git implementation incompatible with the new TFS 2017 git? Can I use these products together?

Answer 1

I can reproduce your script when cloning a git repository with TFS 2015, no problem at all. But when cloning a git repo from TFS 2017, GitKraken always asks for a login:

I also tried the git clone command from the command line after entering the TFS 2017 username and password, it can successfully clone the repo.

It is suggested that you contact GitKraken to report this issue.

Answer 2

The new version 2.1.0 of GitKraken will solve the problem for us; Release Notes: https://support.gitkraken.com/release-notes/current

Answer 3

After doing some research and supporting the gitkraken call, they seem to have a pretty serious problem. If you are currently connecting with client certificates to tfs, you will have problems. this is because they built gitkraken on NodeGit, which has a dependency on lib2git. This, in turn, has problems with client certificates, which are described in detail here to record the answer in 2015 (which was not updated, says the following

Large browsers support client certificates, but they do not speak Git. This is what libgit2 (sharp) is simply not supported. WinHTTP should support them, so it is theoretically possible to add this feature to Windows, but this is more of a marginal case of functionality.

Gitkraken said there was "little to be done" until it was fixed. We can only hope that since this major can be configured in 2017, it will no longer be considered as an edge.