GitKraken with TFS 2017

Question

I have used GitKraken succesfully with TFS 2015. But after upgrading to Tfs 2017 it cannot pull or push. If i use the https endpoint it always try to login to the server. If i use the SSH endpoint it gives me a "Early EOF" exception.

Can anyone help me if i have to configure something on the TFS 2017, so the Kraken can use that endpoint? How can i find out what's the problem with the SSH endpoint? I cannot find anything related in the logs.

Or the GitKraken implementation of git is not compatible with the new TFS 2017 git? Can anyone use these products together?

Do you have the latest version of GitKraken? Got was updated in 2017... — MrHinsh - Martin Hinshelwood, Dec 01 '16 at 19:26
As you've probably already figured out this problem is limited to GitKraken, and not with the VS Git integration, Git bash, or SourceTree. Haven't tried with Tower. I've asked GitKraken for an update, will post here if anything comes back — SonarJetLens, Jan 17 '17 at 20:10

score 4 · Answer 1 · answered Dec 02 '16 at 08:18

4

I can reproduce your scenario, when clone a git repo from TFS 2015, no issue at all. But when clone a git repo from TFS 2017, GitKraken always ask for login:

I've also tried git clone command from Command Prompt, after type the Username and Password of TFS 2017, it can clone the repo successfully.

It's suggest to contact GitKraken to report this issue.

answered Dec 02 '16 at 08:18

Cece Dong - MSFT

29,631
1
24
39

Given that the problem still exists in February 2017, methinx they're not overtly interested in fixing this. – Rachel Ambler Feb 03 '17 at 20:51
I've issued a pro support request for this because I get a certificate issue. – krystan honour Feb 14 '17 at 13:54
1

february 2018, still a problem ;( whats up guys? – jokab Feb 08 '18 at 08:51
Still a problem in 04.2023 - I contacted them but they told me they will not fix it, but can refund me if I want. – Hooch Apr 13 '23 at 10:42

score 2 · Answer 2 · edited Jun 20 '20 at 09:12

After some research and a support call to gitkraken it looks like they have a pretty serious issue. If you currently connect with client certificates to tfs you are going to have issues. this is because they have built gitkraken on NodeGit which has a dependency on lib2git. This in turn has an issue with client certificates which is detailed here for the record the response in 2015 (which has not been updated says the following

The majors browsers do support client certs, but they don't speak Git. This is something which is just not supported by libgit2(sharp). WinHTTP should support them, so it should be theoretically possible to add this functionality on Windows, but it is rather an edge case of functionality.

Gitkraken said there was "little we can do" until this is fixed. We can only hope that since now 2017 can be configured in this major it will no longer be considered edge.

The way we solved this for the time being was to disable client certificates in iis. — krystan honour, Mar 09 '17 at 23:51

score 1 · Answer 3 · answered Feb 14 '17 at 15:36

1

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

answered Feb 14 '17 at 15:36

Guillaume Lebeau

58
5

didn't solve my issue with it needing a certificate or origin, mind you that maybe an entirely different issue :) – krystan honour Feb 14 '17 at 18:01

GitKraken with TFS 2017

3 Answers3