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

Results screen/nodes in Blue Ocean omits important information

    XMLWordPrintable

    Details

    • Epic Link:
    • Sprint:
      pacific
    • Similar Issues:

      Description

      MN Summary: more information is needed than is exposed currently as steps in blue ocean (and possibly classic, but that isn't clear just yet) - more investigation needed. An unpleasant fallback is to resort to viewing full log, but that isn't obvious or nice.

      It appears that the console output doesn't include the "node allocation" information which is useful when trying to debug systemic issues in Jenkins agents.

      Take this Jenkinsfile which can execute on one of a number of agents. We had some issues where an agent was misbehaving, resulting in failures like:

      WARNING: Failed to execute: select name,version,instanceid   from plugin where month >= 1466636926735         and name NOT LIKE 'privateplugin%'         and version NOT LIKE '%(private)'    order by name,version desc,instanceid because: [SQLITE_IOERR]  Some kind of disk I/O error occurred (disk I/O error)
      

      LOLWUT aside, the beginning of the "classic" Console Output view includes:

      Started by user rtyler
      Replayed #8
      Connecting to https://api.github.com using jenkinsadmin/****** (GitHub access token for jenkinsadmin)
      [Pipeline] node
      Running on kelp in /home/jenkins/agent-workspace/workspace/Infra/infra-statistics/master
      [Pipeline] {
      [Pipeline] checkout
      Fetching changes from 2 remote Git repositories
      Checking out Revision 4c2c3e9a24627421e7cd17d725a7a42bfe5a06e7 (master)
      [Pipeline] tool
      [Pipeline] tool
      [Pipeline] stage (Sync raw data and census files)
      

      A screenshot from the Blue Ocean detail page for this run is attached. Suffice it to say, there is no information in the detail page about what nodes this Pipeline run executed on

        Attachments

          Issue Links

            Activity

            Hide
            jamesdumay James Dumay added a comment -

            We are discussing a more generic solution for this on JENKINS-40466.

            Show
            jamesdumay James Dumay added a comment - We are discussing a more generic solution for this on JENKINS-40466 .
            Hide
            michaelneale Michael Neale added a comment -

            James Dumay as one example, the "error" step emits its string not as step output - so I bet there are other cases. So even some steps may use this. Of course there is all the jenkins plumbing which may not show up in step logs (probably more than just nodes)

            Show
            michaelneale Michael Neale added a comment - James Dumay as one example, the "error" step emits its string not as step output - so I bet there are other cases. So even some steps may use this. Of course there is all the jenkins plumbing which may not show up in step logs (probably more than just nodes)
            Hide
            jamesdumay James Dumay added a comment -

            Michael Neale aside from node info - what else is there thats important?

            Show
            jamesdumay James Dumay added a comment - Michael Neale aside from node info - what else is there thats important?
            Hide
            michaelneale Michael Neale added a comment -

            cc James Dumay - maybe we need to think how we express this stuff that doesn't fit within the flow nodes logs

            Show
            michaelneale Michael Neale added a comment - cc James Dumay - maybe we need to think how we express this stuff that doesn't fit within the flow nodes logs
            Hide
            jamesdumay James Dumay added a comment - - edited

            Michael Neale Vivek Pandey I like the step idea if thats possible. Perhaps Sam Van Oort has some ideas.

            Show
            jamesdumay James Dumay added a comment - - edited Michael Neale Vivek Pandey I like the step idea if thats possible. Perhaps Sam Van Oort has some ideas.
            Hide
            michaelneale Michael Neale added a comment -

            Vivek Pandey I thought this may be of interest while you are digging into bismuth. It would be wonderful if we could surface this extra information as steps. If this isn't possible, perhaps we should close this and either rethink the design to show the full log in some cases, or ... don't know what else.

            Show
            michaelneale Michael Neale added a comment - Vivek Pandey I thought this may be of interest while you are digging into bismuth. It would be wonderful if we could surface this extra information as steps. If this isn't possible, perhaps we should close this and either rethink the design to show the full log in some cases, or ... don't know what else.
            Hide
            michaelneale Michael Neale added a comment - - edited

            [~201604291_tyler] it would be good if you could also look at the classic stage view - to see if it includes it there (I think it includes some detail)

            Based on primitive experiments, it looks like it may include more.

            Show
            michaelneale Michael Neale added a comment - - edited [~201604291_tyler] it would be good if you could also look at the classic stage view - to see if it includes it there (I think it includes some detail) Based on primitive experiments, it looks like it may include more.

              People

              • Assignee:
                vivek Vivek Pandey
                Reporter:
                rtyler R. Tyler Croy
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: