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

IBM zOS Connector not retrieving job RC properly

XMLWordPrintable

      If the joblog is formatted in a special way, zOS Connector fails to retrieve job RC.

          [JENKINS-29173] IBM zOS Connector not retrieving job RC properly

          Alexander Shcherbakov added a comment -

          Will add scan for RC through 'dir' command.

          Alexander Shcherbakov added a comment - Will add scan for RC through 'dir' command.

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: candiduslynx
          Path:
          src/main/java/org/jenkinsci/plugins/IBM_zOS_Connector/zFTPConnector.java
          http://jenkins-ci.org/commit/zos-connector-plugin/8a9897db01eb829bec7ac94cee471987508cf3a7
          Log:
          Fix for JENKINS-29173.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: candiduslynx Path: src/main/java/org/jenkinsci/plugins/IBM_zOS_Connector/zFTPConnector.java http://jenkins-ci.org/commit/zos-connector-plugin/8a9897db01eb829bec7ac94cee471987508cf3a7 Log: Fix for JENKINS-29173 .

          Alexander Shcherbakov added a comment -

          Wait for response about fix.

          Alexander Shcherbakov added a comment - Wait for response about fix.

          mesa added a comment -

          Still get Build step 'Submit zOS Job' marked build as failure

          mesa added a comment - Still get Build step 'Submit zOS Job' marked build as failure

          mesa added a comment -

          IMO, you should not scan for return codes, but for system messages. We do not use a "joblog formatted in a special way" as you state above, but our tests system even just logs the out-of.the-box system messages. We do not run installation exits and/or job log formatter. I know many z/SO installation do have stuff like that, but they all vary, and a generalized tool like this plugin shouldn't rely on anything but the plain system message.

          My proposal: Scan only SYSMSGLG for IBM system messages IEF404I, IEF450I, IEF451I, IEF453I. I started to describe and discuss this approach on http://ibmmainframes.com/viewtopic.php?p=330349, and there is yet a better idea to be found.

          mesa added a comment - IMO, you should not scan for return codes, but for system messages. We do not use a "joblog formatted in a special way" as you state above, but our tests system even just logs the out-of.the-box system messages. We do not run installation exits and/or job log formatter. I know many z/SO installation do have stuff like that, but they all vary, and a generalized tool like this plugin shouldn't rely on anything but the plain system message. My proposal: Scan only SYSMSGLG for IBM system messages IEF404I, IEF450I, IEF451I, IEF453I. I started to describe and discuss this approach on http://ibmmainframes.com/viewtopic.php?p=330349 , and there is yet a better idea to be found.

          Alexander Shcherbakov added a comment -

          Now RC is scanned correctly.

          Alexander Shcherbakov added a comment - Now RC is scanned correctly.

          mesa added a comment -

          Added feature request in JENKINS-29214 to allow non-zero return codes to be considered success.

          mesa added a comment - Added feature request in JENKINS-29214 to allow non-zero return codes to be considered success.

            candiduslynx Alexander Shcherbakov
            candiduslynx Alexander Shcherbakov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: