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

error step has no log output

XMLWordPrintable

      if you use "error 'help'" in a pipeline, the pipeline will exit. The text 'help' appears in the overall log, but not in the log for the step/node.

          [JENKINS-39337] error step has no log output

          Michael Neale created issue -

          Jesse Glick added a comment -

          As designed. It throws up an exception. Whoever catches that exception may choose to log it, or not. If the exception terminates the build, the build log shows it. ErrorAction can be used to determine which steps terminated with this exception.

          Jesse Glick added a comment - As designed. It throws up an exception. Whoever catches that exception may choose to log it, or not. If the exception terminates the build, the build log shows it. ErrorAction can be used to determine which steps terminated with this exception.
          Jesse Glick made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          Michael Neale added a comment -

          How is this designed at all? if it just throws an exception, why does this step exist? it doesn't provide anything extra over throw Exception("message here")?

          It should at least log the message, or else be removed as a step with no purpose.

          Michael Neale added a comment - How is this designed at all? if it just throws an exception, why does this step exist? it doesn't provide anything extra over throw Exception("message here")? It should at least log the message, or else be removed as a step with no purpose.
          Michael Neale made changes -
          Resolution Original: Not A Defect [ 7 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]

          Jesse Glick added a comment -

          why does this step exist? it doesn't provide anything extra over throw Exception("message here")?

          new hudson.AbortException('message') specifically, which is not whitelisted, and not really something a user would be expected to know about. There is also an open RFE to allow you to set the build status, which would be an even more torturous and non-whitelisted construction if you had to do it by hand.

          It should at least log the message

          No, it should not. It is up to the catcher to decide whether and how to respond to an exception.

          Jesse Glick added a comment - why does this step exist? it doesn't provide anything extra over throw Exception("message here") ? new hudson.AbortException('message') specifically, which is not whitelisted, and not really something a user would be expected to know about. There is also an open RFE to allow you to set the build status, which would be an even more torturous and non-whitelisted construction if you had to do it by hand. It should at least log the message No, it should not. It is up to the catcher to decide whether and how to respond to an exception.
          Jesse Glick made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Reopened [ 4 ] New: Resolved [ 5 ]
          ethorsa made changes -
          Link New: This issue is related to JENKINS-58597 [ JENKINS-58597 ]

            Unassigned Unassigned
            michaelneale Michael Neale
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: