So I updated both the "ssh" and "git" capabilities on my 3.4.4 server to point to the local binaries. What seems goofy to me is that I am still getting "auth fail" from jsch on my plans... we control which key is used through .ssh/config and it is working just fine from command line.
I suppose I would like to understand what circumstances would cause Bamboo to ignore my defined executables and fall back to its java implemented roots...
Even when a native git capability is defined, Bamboo uses jgit for some operations - for example checking the remote tip hash. You still have to define the authentication data properly inside Bamboo to work with your Git repository, making it work from the command line is not sufficient.
Ahh, very interesting. I think that this might be a design issue then... I will submit a feature request to allow for full native binary usage (optional elimination of jgit). This will allow us to also define other ssh options, such as ConnectionAttempts...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
$ ssh -V
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
$ git --version
git version 1.7.2.3
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.