|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
As anyone tried to add some standard Jenkins debugging for the remoting element ?
For example, following https://wiki.jenkins-ci.org/display/JENKINS/Logging
1. Go to Jenkins / Manage Jenkins / System Log
2. add a new log recorder, e.g. named "Remoting"
3. add a logger, with name hudson.remoting, level FINEST
4. optional add another Logger for anything unity3d related (org.jenkinsci.plugins.unity3d / FINEST)
5. save it
Check that it works (you should start seeing logs appear as soon as some slaves are involved).
When the bug triggers, look at the logs and add them here or send them privately to me.