I'm still not able to duplicate this with the current code. Automated and interactive tests of JGit with an RSA private key continue to run correctly on Windows, Ubuntu 12, Ubuntu 14, Debian 7, Debian 8, Debian 9 pre-release, CentOS 6, and CentOS 7. The tests uses private git repositories on assembla, bitbucket, gitlab, github, and on two different private computers that I host at home.
I have 2 JGit based failures in the automated test suite that are only visible when using the git client plugin 1.20 beta and the git plugin 2.5 beta with submodule authentication configured to use the credentials of the parent repository. If that's the case you're seeing, please share that information.
If you have more details, or a publicly accessible way to duplicate the bug, I'm certainly interested. I'm also interested if you've been able to successfully connect to the same repository with command line git rather than JGit.
|