If you use the Git for Windows installer, it offers 3 choices for how you
can modify your PATH to include git. If you install in "Program Files"
(rather than a thumbdrive install) and choose to at least be able to run
git from the Windows command prompt (the middle choice), then you shouldn't
need any further configuration globally or locally.
If you choose to not modify the PATH to allow Windows command prompt to run
git, then the git plugin doesn't (currently) attempt to make guesses about
the location of the git executable.
On Tue, Sep 20, 2016 at 12:19 PM Steve K <steve.kerxha...@carestream.com>
> Thanks Mark. That does seem to have done the trick.
> I had added the Git location on a Global basis (via. Manage Jenkins -->
> Configure System) but that didn't help.
> I'm a little disappointed that I have to deal with this on a per-agent
> basis (we didn't need to do that when using a v1.625.3 Windows master),
> but, if it works, it works.
> Thanks again.
> Steve K.
> 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
> 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 view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.