Why is Jenkins getting Authentication Failed error for git submodule update?
I have a Jenkins job that pulls from a BitBucket repo that was working fine, and still is. However, I’ve added a submodule and Jenkins is choking on that. Here is a clip from the Jenkins console output:
FATAL: Command “C:\Program Files (x86)\Git\cmd\git.exe submodule update” returned status code 1:
stdout: Cloning into ‘submodules/my.repo’…
Permission denied (publickey), when cloning bitbucket repository via ruby-script Change Credentials for Push in Git Can SonarQube fetch Data from a Git Repository? Same code different git files, merging with keeping history Git Push Error | Bitbucket Repository How to push Tag to Bitbucket Git Repository in Bamboo from Cake build task?
stderr: fatal: Authentication failed
I’m using an ssh key which I added to my deployment keys for the main repo in BitBucket. And that’s always worked. I added the same key to my submodule repo’s deployment keys. Can anyone tell me why authentication is failing?
4 Solutions collect form web for “Why is Jenkins getting Authentication Failed error for git submodule update?”
Try to copy the /.shh folder into your Jenkins home directory.
I faced this issue, with Jenkins Slave (executed as Windows Service).
I solved it by deploying Jenkins SSH key in the
.ssh directory of the
SYSTEM home directory varies depending on OS version and setup. To identify it just echo env. var.
git config –global credential.helper wincred
Versions of the Jenkins git plugin prior to 3.0.0 did not support submodule authentication. Submodule authentication using the same credentials and protocol as the parent repository are now supported with the Jenkins git plugin. Support was added in the 10 Sep 2016 release of Jenkins git plugin 3.0.0.
The submodule configuration portion of the job definition page (“Additional Behaviours” > “Advanced Sub-modules Behaviours”) “now includes a checkbox “Use credentials from default remote of parent repository”. Check that box and the credentials from the parent repository will be used for the submodules.
Note that the repository cloning protocols must be the same (ssh or https) for the parent repository and the submodules, otherwise the parent credentials can’t be used with the submodule repository.