Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Component/s: git-client-plugin
-
Labels:
-
Environment:Jenkins:2.222.3
git-client: 3.3.1
git-plugin: 4.3.0
z/OS R2.4
git 2.14
-
Similar Issues:
-
Released As:3.4.0
Description
When attempting to clone a repository using an SSH key-pair in a pipeline, the clone fails with
Permission denied (publickey).
if the key has a passphrase. The authentication succeeds if there is no passphrase. Various encodings have been attempted to get past this, including utf8, ISO8859-1, and IBM-1047.
We are using an SSH Agent as a workaround for the time being, but that requires manually modifying the git configuration in new workspaces.
Mark Waite We have been using the fix for a week with no issues. I can confirm that the SSH key-pair is correctly authenticating with this option. The repository format recognition is a completely separate issue and unrelated. So the entire use case is working.