On 08/01/2012 07:21 AM, Gavin Davies wrote:
The slaves need access to the keys on the master Jenkins server to be able to check out from a Git repo that uses SSH key authentication; we don't want to have to manually put the keys on all the slaves if possible.
Without answering your question, I will note that with the Mercurial plugin the corresponding problem is most easily solved by clicking the "Use Caching" option for the Mercurial installation. This builds a mirror of the remote repo on the master node and then transfers changeset bundles to slaves on demand using the remoting channel. While the primary purpose of this feature is to avoid redundant network activity when lots of jobs are building from a handful of repos, a corollary benefit is that slaves need no special authentication keys - or even general network access. I presume the same could be done for the Git plugin using git-bundle.
