It doesn't seem practical for build artifacts to have their encodings changed automatically; doing so would require that the Jenkins slave code somehow be told which files are safe to convert and which are not. The log is a different situation, of course; that would be safe to convert (and to do so on the fly).
----- Original Message ----- From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Nov 22 2013 16:50:04 Any updates on this? I'm in the same boat. The slave.jar connects just fine with no special encoding, but any artifacts created on z/OS USS side come back to the Jenkins server as EBCDIC and so does the log file found on the server (even though it won't display on the web page). Thanks! Dave (dorcus) -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
