Jenkins - Git error: FATAL ERROR: Disconnected: No supported authentication methods available (server sent: publickey)

365 views
Skip to first unread message

Andrew

unread,
Dec 20, 2016, 2:19:49 AM12/20/16
to Jenkins Users
Hi

Wondering if anyone can assist with this error.  Setting up a new Windows 7 Jenkins server after the old one crashed irrevocably.

Job definition (when openning Configure) on the GIT Repo is reporting

Failed to connect to repository : Command "C:\Program Files (x86)\Git\bin\git.exe ls-remote -h g...@github.aus.ourcompany.com:FX/fx-ods HEAD" returned status code 128:
stdout
:
stderr
: FATAL ERROR: Disconnected: No supported authentication methods available (server sent: publickey)

fatal
: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Various readings and troubleshooting, but no resolution. So far have done:

- SSH key loaded into pageant.exe before jenkins starts (as a windows service - delayed start)
- from command line, this command works and returns 0 (though had to quote command)
- can clone (using GIT Extensions) repository fine
- have run ssh -T g...@github.aus.ourcompany.com and responded Yes
- git and maven configured in Global Tools Configuration
- environment variable GIT_SSH to GitExtensions (32b) plink.exe exists
- using GitExtensions (32b) pageant.exe to cache SSH ppk file
- HOME=C:\Users\SpecialUser
- Service running as SpecialUser that has
- GIT has SSH id_rsa.pub loaded
- Rebooted server to ensure all these changes have been picked up
- Path has GIT\bin in it, but removing the path to the error command has no impact - same error.
- Manage Jenkins | System Info is reporting the HOME, GIT_SSH and path same as what command line reports


Everything I've read gets to where I've got to, but assumes it is now working in Jenkins - but its not. Short of moving all of the Jenkins, Java, Maven, Git, etc out from under C:\Program Files (x86) to say C:\Apps\ to remove spaces as a cause, I'm at a loss on how to proceed.  There is no debugging I can see on the git.exe that might report exactly what is going wrong.

Thanks ... Andrew
Reply all
Reply to author
Forward
0 new messages