Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
durable-task-1.10
-
-
durable-task 1.29
Description
We are going to use the pipeline plugin with build nodes running under z/OS Unix System Services (USS). Unfortunately, the sh step does not work out of the box on that platform because (text) files are encoded by default in IBM1047 (some EBCDIC variant) but the implementation within the durable-task-plugin seems to assume implicitly that the shell input and output is in UTF-8 or ASCII based.
First experiments on top of durable-task-1.10 adding character set conversion in BourneShellScript and FileMonitoringTask to any read/write of files script.sh, pid, jenkins-result.txt and jenkins-log.txt were promising.
Update : - the Script.sh file is untagged in z/OS USS , if its tagged as ASCII the script can be executed in z/OS USS. when the script is pushed it need to be tagged as ASCII.
Attachments
Activity
PR 80 was merged, so z/OS support will be available in the next release.
This feature was just added in version 1.29 of the Durable Task plugin.
Anu George
added a comment - I was trying to use this plugin to execute a sh file in z/OS USS, but gives error, so I just tried a simple step as below
pipeline {
agent { node
}
stages {
stage('build') {
steps
}
}
}
even this does not work. If anyone can give me suggestions, it will be helpful. Thanks in advance
Anu George
added a comment - I was trying to use this plugin to execute a sh file in z/OS USS, but gives error, so I just tried a simple step as below
pipeline {
agent { node
{ label 'KanplexUSSAgent' }
}
stages {
stage('build') {
steps
{
sh 'pwd'
}
}
}
}
even this does not work. If anyone can give me suggestions, it will be helpful. Thanks in advance
Lutz Neugebauer
added a comment - try
sh(encoding:'IBM1047', script:'pwd')
for the shell step Thanks lne , I tried the below and it still doesn't work, same error
pipeline {
agent { node
}
stages {
stage('build') {
steps
}
}
}
Anu George
added a comment - - edited Thanks lne , I tried the below and it still doesn't work, same error
pipeline {
agent { node
{ label 'KanplexUSSAgent' }
}
stages {
stage('build') {
steps
{
//sh 'pwd'
sh(encoding: 'IBM-1047', script:'pwd') }
}
}
} Lutz Neugebauer
added a comment - IBM1047 vs IBM-1047 doesn't make a difference at my end. So you might want to double check your plugin versions. Here it is running fine with:
- durable-task 1.29
- workflow-durable-task-step 2.24
- workflow-job 2.21
Due to the error message you might also want to check whether IBM1047 is supported by the involved JVMs.
Lutz Neugebauer
added a comment - IBM1047 vs IBM-1047 doesn't make a difference at my end. So you might want to double check your plugin versions. Here it is running fine with:
durable-task 1.29
workflow-durable-task-step 2.24
workflow-job 2.21
Due to the error message you might also want to check whether IBM1047 is supported by the involved JVMs.
Anu George
added a comment - I am curious, do we need all three plugins for this to work. I do have all, but just checking. thanks . I need to check whether IBM1047 is supported.
Anu George
added a comment - I am curious, do we need all three plugins for this to work. I do have all, but just checking. thanks . I need to check whether IBM1047 is supported. 
I am stumbling over exactly the same issue using Multibranch Pipelines. It seems to me that either script.sh needs to be created in the native character encoding, or script.sh should be tagged in z/OS UNIX System Services filesystems as ASCII. Writing in the native character encoding seems, to me, to be a more generic implementation. Maybe this is z/OS unique and it doesn't matter how it is implemented ...
I have not found any possible workaround. For a Freestyle project, you set Java environment variables and the Java slave takes care of it.