-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Jenkins 1.598
Linux 2.6.32-431.5.1.el6.x86_64
CentOS release 6.5 (Final)
Plugins:
Attached file saved from pluginManager/api/xml?tree=plugins[shortName,version]&pretty
I have a private key set up in the global credentials (named sls). I have the SCM for a test project set up to download code from a springloops git project. See attached log of the failure to connect to git.
Fetching the repo with command line git works fine with the same key. If I install an SSH agent on the exact same build, it allows the fetch to work. See the other attached log for that.
I have used jenkins and git in a different environment with no problems. The only difference I've noticed here is the non-standard port of 1234. Is it possible git plugin is not identifying the port?
Setting the priority to major since use of SSH agent is a workaround but requires extra configuration and build overhead.
- duplicates
-
JENKINS-20879 SSH Credentials (private key with passphrase) do not work
-
- Closed
-
- is duplicated by
-
JENKINS-20638 SSH key credential doesn't work with key passphrase
-
- Closed
-
[JENKINS-27998] Git plugin fails to clone with ssh protected passphrase
Link |
New:
This issue duplicates |
Summary | Original: Git plugin fails to connect | New: Git plugin fails to clone with ssh protected passphrase |
Link |
New:
This issue is duplicated by |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 162599 ] | New: JNJira + In-Review [ 196999 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |