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

Errors on block-scoped steps not represented in Blue Ocean

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • blueocean-plugin
    • None
    • Blue Ocean 1.1.4, core 2.66 or something...
    • Blue Ocean - Candidates

    Description

      When you've got a Pipeline like:

      stage('foo') {
          node {
              withCredentials([string(credentialsId:'not-real', variable:'WHO_CARES')]) {
                  echo "This will never happen."
              }
          }
      }
      

      You'll get a page like the attached screenshot - there's an error, specifically in withCredentials because I gave it a bogus credential ID - but since withCredentials isn't an atomic step, it's not represented on its own in the Blue Ocean UI. So it looks like no steps were run and there's nowhere to find the error!

      In the second case, with a slightly different Pipeline:

      stage('foo') {
          node {
              echo "splode"
              withCredentials([string(credentialsId:'not-real', variable:'WHO_CARES')]) {
                  echo "This will never happen."
              }
          }
      }
      

      ..there's a step that ran before the withCredentials block, so even though it actually succeeded, it's now marked as failed and there's still no way to find the actual log for the withCredentials error!

      Attachments

        Issue Links

          Activity

            stilllman Luc Touraille added a comment -

            I would like to bump this issue, as it makes the Blue Ocean logs very hard to work with: we always need to go back to the classic UI to be able to see all the logs.

            Our pipelines contain more wrapper steps than atomic steps, usually we have one or two "sh" or "bat" + a "copyArtifacts" within "node", "timeout", "withCredentials", "dir", "withEnv", "withPythonEnv", "sshagent" etc. All these wrapper steps provide logs that are very useful to troubleshoot CI issues, and currently they cannot be seen anywhere from Blue Ocean, and we have to go back to the classic log or Pipeline Steps to actually see them.

            Is there any plan to work on this issue?

            stilllman Luc Touraille added a comment - I would like to bump this issue, as it makes the Blue Ocean logs very hard to work with: we always need to go back to the classic UI to be able to see all the logs. Our pipelines contain more wrapper steps than atomic steps, usually we have one or two "sh" or "bat" + a "copyArtifacts" within "node", "timeout", "withCredentials", "dir", "withEnv", "withPythonEnv", "sshagent" etc. All these wrapper steps provide logs that are very useful to troubleshoot CI issues, and currently they cannot be seen anywhere from Blue Ocean, and we have to go back to the classic log or Pipeline Steps to actually see them. Is there any plan to work on this issue?

            People

              Unassigned Unassigned
              abayer Andrew Bayer
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: