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.
It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...
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