I failed to set up Sourcetree to connect to an already running ssh-agent. Is this possibly? If so, how? My Sourcetree always starts its own ssh-agent.
Long story: our Bitbucket Server is behing another host we connect to with SSH. Therefore we use something like the following in ~/.ssh/config:
This works really well with GNU/Linux and with Windows using OpenSSH. For key management however we use PuTTY and pageant on Windows. Git comes with a ssh-pageant.exe and a start-ssh-pageant.bat script to launch the ssh-pageant.exe which talks OpenSSH to git but fetches the keys from PuTTY's pageant.
This works perfectly with TortoiseGit, Git for Windows on the command line, but it fails with Sourcetree because Sourcetree insists in launching its own ssh-agent instead of using the one already running.
Is there a way (environment variable, configuration option, etc.) to tell Sourcetree to use OpenSSH, but NOT start an own ssh-agent, but use an already running agent?
Supported Platforms macOS Windows We recently introduced support for additional hosting services such as GitHub Enterprise, GitLab (Cloud, Community Edition, Enterprise Edition), and...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG