It seems like you'd use the credentials plugin[1] to configure one or more ssh keys copied from the Gitlab UI to the Jenkins credential, then the jobs would be configured to use one of those credentials and to use ssh based access to read from the git repositories hosted on the Gitlab server.
We use ssh to communicate with our git server, and it works quite well. Mark Waite [1] https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin On Sat, Nov 2, 2013 at 4:35 AM, Philipp Kraus <philipp.kr...@flashpixx.de>wrote: > Hello, > > I run a Jenkins master on an Ubuntu server, in the firewall only SSH, > HTTP, HTTPS ports are openend for incomming communication. I have read > https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds for > distribution builds, but on my master I use LDAP for user authentification. > On the systems also runs GitLab and a SSHd with key-based authentification. > My question is, in which way communicate the Jenkins slaves with the > master? I would like to run slaves with Linux, OSX & Windows, but I would > like to use SSH (SFTP) only for a key-based authentification. The keys > should be inserted by the GitLab UI interface and this keys should be also > used by Jenkins. > > Any idea / help to create a solution for this problem? > > Thanks > > Phil > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
