When cloning a repository with a port number in the URL, Sourcetree is unable to read the remote repository.
This is an example of the repository being cloned.
ssh://git@git.platform.company.io:2222/repo_name/repo_name.git -v
Error: plink: unknown option "-p"
fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
Sourcetree 2.5.5.0 is TortoiseGit: 2.5.0.0 is running concurrently with Git v.2.16.2 and OpenSSH_7.6p1.
TortoiseGit will push/pull/clone OK. SourceTree is unable to see the remote repository.
Previously TortoiseGit received "Fatal: ssh variant ‘simple’ does not support setting port." Adding git config --global ssh.variant to the Git config allows Tortoise to push/pull/clone. We can get either Tortoise or Sourcetree working individually, but not together.
The problem is both versions of TortoiseGit and Sourcetree of with different version numbers were working well together prior to the Git v 2.16.2 update.
I've done as much troubleshooting and tweaking as possible. Both the system git and embedded git are at 2.16.2. SourceTree 2.5.5.0 does not seem to differentiate between the System Git and Embedded Git.
Embedded git points to: C:\Users\connolr\AppData\Local\Atlassian\SourceTree\git_local\cmd\git.exe
System Git also points to: C:\Users\connolr\AppData\Local\Atlassian\SourceTree\git_local\cmd\git.exe
The expected behavior would be C:\Program Files\Git\bin\git.exe
Is SourceTree reading Putty instead or plink? TortoiseGit seems to read the public/private key pair OK, but Sourcetree seems to not recognize it. Is there a setting or something to add in the config file that allows SourceTree function concurrently with TortoiseGit and bash?
Thank you.