You could enable JGit as a git implementation from the master Jenkins configuration page, then use JGit as the implementation for your jobs. That avoids deploying git on each slave.
JGit is not as full featured in the plugin as command line git, but it is sufficient for many uses. Alternately, you can install command line git on each slave, then let the git plugin use its default, command line git. Mark Waite On Mon, Aug 17, 2015 at 7:07 PM moodysma sma <moody...@gmail.com> wrote: > Hi, > > I'm new to jenkins. I want to understand what is the proper way to deploy > git to slaves. I have a git repo on a server, I want to build on a master > node which is different from the git repo. Then I want to deploy a clone > repo on all the slaves. Is it better to clone on the slaves or just > transfer the files? I'm able to checkout on the master from the repos but > I can't seem to get the clones on the slaves working. Any help would be > appreciated. > > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/da8be4a7-3dd3-4af7-9e3c-5d4a21387127%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/da8be4a7-3dd3-4af7-9e3c-5d4a21387127%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHUTx7kvFNbtZeBd0CtTvdq51tgmmZhmJ3-1vwPA8T1CA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
