We're trying to use Jenkins to build our software on OS/390 (using the Hercules emulator, not real hardware, but still). This OS uses EBCDIC as its native character set, not ASCII. We've successfully managed to check out from our SVN repository (yay!), but now we would need to run commands to build the software. And this is where we run into problems ...
The problem is that commands that we type into the text field of the "Execute shell" build step need to be translated from ASCII to EBCDIC when run on the OS/390 side. We confirmed that this is the problem by manually translating a simple command to EBCDIC and typing those characters into the text input field - the command was then executed. However, a lot of EBCDIC characters have non-printable ASCII equivalents, so this is not an option in practice (besides it being a pain in the back to maintain). Is there any any plugin that can handle this situation? Alternatively, is there a plugin that would simply let us run a script that's already on the OS/390 side? Please note that again, there's the problem of character set translation - this time with the file name; but since the SVN plugin does work as expected, maybe some part of Jenkins is already doing the right thing. We're stuck at this point, so any help is appreciated. Thank you. bye, Dirk -- 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.
