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.
Attachments
Issue Links
Activity
Thanks. Then all I need to do is add the documentation that describes the property. That's a good excuse to document the other properties provided by the plugin as well.
Randall Becker I've added documentation for the other properties. Does the layout look reasonable to you? If so, then I'll submit a pull request for that documentation, then once it is merged, I'll update the docs in the PR for this property.
I like the format. Actually learned something about tags that I was annoying - I want my tags being updated silently as long as they are verified. Side issue. Go for PR 
Randall Becker
added a comment - I like the format. Actually learned something about tags that I was annoying - I want my tags being updated silently as long as they are verified. Side issue. Go for PR Released in git client plugin 3.4.0 with the properties documented in plugin properties
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.