![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
stephenconnolly
|
|
Components:
|
ssh-credentials |
|
Created:
|
18/Nov/13 9:26 PM
|
|
Description:
|
Adding a SSH key credential enables an executor on the master to use the credential for cloning a Git repository via SSH using the provided credentials. The private key is stored in ~/.ssh of the Jenkins user.
Running the same job on a SSH slave, the expectation is that this will work as on the master without any further configuration action.
This is not the case, the job will fail with the following in the log:
stdout: Cloning into '/home/jenkins/workspace/Begin_Release'...
stderr: Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,password).
fatal: The remote end hung up unexpectedly
I would expect the SSH key credentials to be transferred to the slave so that they can be used there, too. Instead, the private key has to be installed in the ~/.ssh directory on the slave, too.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Florian Zschocke
|
|
|
|
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/groups/opt_out.
