I wasn't aware of that advanced option to set JVM arguments when running a slave. Nice feature.
I was able to confirm that the arguments are honored when used with a slave started through ssh and that they are not honored by a slave running as JNLP. I think you'll need to submit a bug report. Mark Waite On Wed, Nov 5, 2014 at 2:46 PM, Dunnigan, Terrence J < [email protected]> wrote: > Hi all, > > > > We have some Windows 7 slaves, connected via JNLP, that don’t recognize > the git timeout values. > > > > Specifically, we are passing the JVM option > “-Dorg.jenkinsci.plugins.gitclient.Git.timeOut=120”. This option works on > our slaves that we control via a Windows Service, but for some reason it > doesn’t do anything for the slaves that we control via JNLP. > > > > Has anyone seen this issue before? > > > > Jenkins LTS 1.554.3 > > Git plugin 2.2.2 > > Git client plugin 1.10.0 > > > > Thanks! > > > > Terry > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Thanks! Mark Waite -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
