|
||||||||||||||
|
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.
Given the age and nature of this issue and the comments indicating this is partly fixed or actually several issues, I'm resolving this as Cannot Reproduce.
This doesn't mean the issue reported here isn't valid or anything like that. But Jenkins has been improved a lot in the mean time, so the value of this issue report is questionable by now (is it still relevant? Who knows?). It seems this slipped through the cracks as it was filed against a completely unrelated component (the Slave Setup Plugin).
If you encounter similar issues in then-recent Jenkins versions (say, no older than eight weeks), please file a new issue against the remoting component following the instructions here: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue