|
||||||||
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.
When I read relevant part of the core source code, I think it handles the situation correctly where the encoding of the master and the slave are different.
During a recursive copy, files are packed into a tar format with what's known as "GNU-style long file name" extension, which stores file names in UTF-8. The master reads them back as such and then tries to create files of the same name.
I suspect the master JVM's default encoding is set to iso-8859-1 or something that cannot map some non-ASCII characters. I recommend you check the LANG environment variable on the master JVM.