![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
ssh-agent-plugin |
|
Created:
|
28/Mar/15 3:38 AM
|
|
Description:
|
Original problem discussed in ticket JENKINS-27655 against perforce-plugin. After discussion and investigation, I found that a similar problem for the git-plugin was fixed in ssh-agent-plugin for JENKINS-12492, so I'm refiling this bug against ssh-agent-plugin.
Quick summary is that I have my ssh key credential loaded properly into ssh-agent-plugin, and while the key is available to the build steps themselves (such as a shell execution), the key is NOT available to the SCM/perforce step that comes before.
|
|
Environment:
|
Ubuntu linux, chrome, Jenkins 1.606, perforce-plugin 1.3.34, ssh-agent-plugin 1.5
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
David Young
|
|
|
|
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
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
