-
Bug
-
Resolution: Fixed
-
Blocker
-
Jenkins:2.222.3
git-client: 3.3.1
git-plugin: 4.3.0
z/OS R2.4
git 2.14
-
-
3.4.0
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.
[JENKINS-63146] Pipeline Clone fails on zOS with SSH Key-pair with Passphrase
Assignee | Original: Mark Waite [ markewaite ] |
Component/s | Original: git-plugin [ 15543 ] |
Remote Link | New: This issue links to "PR-585 - set character set based on environment variable (Web Link)" [ 25350 ] |
Remote Link | New: This issue links to "PR-584 - set passphrase character set based on ibm.system.encoding property (Web Link)" [ 25351 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Assignee | New: Mark Waite [ markewaite ] |
Attachment | New: git-client-3.3.2-PR-584-ibm.encoding.property.hpi [ 51999 ] |
Attachment | New: git-client-3.3.2-PR-585-credentials-file.encoding.hpi [ 52000 ] |
Comment | [ I have to completely rebuild my entire Jenkins agent structure. The dependencies of this fix appears to have caused all agent configurations to be lost. This is going to take a lot of time - as in days. I don't know what happened or how to recover. ] |