On Tuesday, 23 June 2015 15:13:47 UTC-5, Steve Robbins wrote: > > > The stack trace (below) is slightly different but it seems very similar to > https://issues.jenkins-ci.org/browse/JENKINS-19075 Unfortunately, the > suggestion to use "-Djcifs.resolveOrder=DNS > -Djcifs.smb.client.dfs.disabled=true" did not work for me. [Just to be > certain: I used those arguments on the slave node that was failing. I > presume that is where the "publish" is running, right? Or do I need to > modify the master node's options? If so, how do you accomplish that when > the service runs jenkins.exe?] >
So it turns out that you do indeed need to modify the arguments on the MASTER node, not the SLAVE. Once I did that (edit jenkins.xml), the problem went away. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4a49d654-824b-4dc1-843a-e577944ae87f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
