Workaround

You can work around this problem by creating a passwordless SSH key in the "default" location for the jenkins user (in my case that is `/var/lib/jenkins/.ssh/id_rsa`) which has read only access to the repository. The idea of a passwordless SSH key in a "secure" environment is generally frowned upon, but the only thing we grant it access to is read only to the repo.

sudo -Hu jenkins ssh-keygen -t rsa
# (hit enter three times to accept the default filename and blank password twice)

NOTE: If you wanted to be a bit more secure, you could use a different filename for the SSH key (such as `/var/lib/jenkins/.ssh/id_rsa-insecure`) and then modify your `/var/lib/jenkins/.ssh/config` so that only your git server uses that key, but as long as it is not granted access to anything else, it should be "secure enough" ... I guess this would really be useful if you already have a default SSH key used for other purposes. If you need to do that, you probably already know how

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.

Reply via email to