![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Nicolas De Loof
|
|
Attachments:
|
git_bug_build.log, git_bug_build_with_ssh_agent.log, plugins.xml |
|
Components:
|
git-plugin |
|
Created:
|
17/Apr/15 4:45 PM
|
|
Description:
|
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.
|
|
Environment:
|
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
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Jamie Doornbos
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/d/optout.
