Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-37341

Add support of z/OS USS to sh step

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: durable-task-plugin
    • Labels:
      None
    • Environment:
      durable-task-1.10
    • Similar Issues:
    • Released As:
      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

          Issue Links

            Activity

            Hide
            kepler2 Bruce Griffith added a comment -

            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.

            Show
            kepler2 Bruce Griffith added a comment - 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.
            Hide
            dnusbaum Devin Nusbaum added a comment -

            PR 80 was merged, so z/OS support will be available in the next release.

            Show
            dnusbaum Devin Nusbaum added a comment - PR 80 was merged, so z/OS support will be available in the next release.
            Hide
            dnusbaum Devin Nusbaum added a comment -

            This feature was just added in version 1.29 of the Durable Task plugin.

            Show
            dnusbaum Devin Nusbaum added a comment - This feature was just added in version 1.29 of the Durable Task plugin.

              People

              • Assignee:
                Unassigned
                Reporter:
                lne Lutz Neugebauer
              • Votes:
                2 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: