|
||||||||
|
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/groups/opt_out.
I had the same problem and the issue was with environment variables
the slave was running on a linux machine, started via ssh from master but the jvm process on the slave didn't get the environment parameter set up for the slave
you can check by doing
sudo cat /proc/[slave_pid]/environ
so I added 'Prefix Start Slave Command' of
export LANG=en_US.UTF-8;
restarted slave, and checked to see if it was set in /proc/?/environ
after that it did do the svn co correctly