|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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.
Success!![]()
Thank you very much.
The certificate on Subversion was issued by our CA so I don't think that applies, however I did get one slave to build just now by adding the -Djsse.enableSNIExtension=false argument in to the slave.xml file.
<arguments>-Xrs -Djsse.enableSNIExtension=false -jar "%BASE%\slave.jar"...
That looks like it'll get the jobs running again to me, I'll apply it to the other slaves but when I go to configure the job in Jenkins it still gives me E175002 as shown above, despite it then working on the slave. Do you know how I can apply the same fix to my Jenkins server? I don't see a java.exe process so I'm thinking that's different?