We have a need to build portable C++ code on OS/390. Our existing builds run on Jenkins so it would be optimal to connect our Z/OS hardware as a slave to our existing master.
>From searching I've found references indicating the need to override the default file encoding and set it to ISO8859_1 via: java -Dfile.encoding=ISO8859_1 -jar slave.jar -text This was the ONLY way I could get the slave to successfully connect to the master, however since the encoding on the slave is no longer IBM1047, any command that is executed on the slave fails with /tmp/hudson8461533719780861058.sh 1: FSUM7351 not found since I'm assuming the generated shell script contains the incorrect encoding. I just recently came across this post yesterday: *https://groups.google.com/forum/#!topic/jenkinsci-users/x1boF8B5flM* which got me a lot closer. I downloaded the jar referenced in the post from: https://ci.jenkins-ci.org/job/remoting/lastBuild/ Using the new remoting.jar, the commands do execute correctly on OS/390 since they now appear to be encoded correctly, however, as the user in that thread mentioned the console log is now empty. I did inspect the log file for that job under $JENKINS_HOME and it does contain EBCDIC encoded characters. Is there a way to get the console output back and in a human readable format i.e. converted back to ASCII? Thanks, Jay -- 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.
