|
||||||||
|
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.
Works for me with a pristine Jenkins 1.600 and new home directory, freestyle job run on master.
Could you try to reproduce this issue on a (mostly) new Jenkins instance, and/or try to figure out what part of your environment breaks this? Maybe there's something interesting in the slave log? jenkins.log? The system logs of the slave node?