Change By: Jay Hayes (02/Jul/13 2:37 PM)
Description: This issue addresses the console log failing to display the log from a job executed on a Z/OS slave.  I have debugged jenkins using the 1.519 src and discovered the physical log file is being written to disk and encoded as IBM1047.  If the log file itself is viewed, you will find CR (carriage return) characters at the end of each line.  If those characters are converted to either CR/LF pairs or just LF characters the log file is once again view-able by clicking the console log link.  For testing purposes, I added a method to scrub the log file (modify the CR's as noted above) if the encoding is set to IBM1047 and call the method from within onEndBuilding() in hudson.model.Run.  I can now view the log file via the console log after the build completes.

I'm attaching the build.xml and log from a Z/OS job run for reference.


Also, see this post for additional info:
https://groups.google.com/forum/#!searchin/jenkinsci-users/EBCDIC/jenkinsci-users/OUdnqAaJjiE/hmvZBY9DUcYJ
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.
 
 

Reply via email to