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

Developer wants to see a message when Jenkins is busy eg: execution is blocked waiting for a node

    Details

    • Similar Issues:
    • Epic Link:
    • Sprint:
      frank, tethys, christmas, pannonian

      Description

      Problem
      When Jenkins is working, for example waiting for a node, a user is given no feedback as to what is happening. Currently this is a generic "waiting for run to start" message.
      This is not captured in any steps logs currently.

      What we want to see
      We want to show an appropriate message when a Pipeline is waiting for a node "Waiting for a node labeled XYZ to become available", and any other missing information that is not currently surfaces in step logs.

      Examples
      For example with a simple pipeline:

      node ('does not exist or busy') {
        sh 'echo hello world'
      }
      

      which currently looks like:

      In classic console it shows:

      Started by user mic
      [Pipeline] node
      Still waiting to schedule task
      Waiting for next available executor
      

      Ideally we can surface this information (who started it) but also that it is waiting for an executor, but also what the label expression/other deatils are.

      This should happen anywhere a node is requested (as one example) not just at the start of a build (so not an empty state).
      This could surface as a flownode which could be shown similar to a step (a synthetic step?)

      Another example:

      kzantow/failure-broject - branch name "michaelneale-blockscoped" when running that, the following information is omitted which could be useful:

      Started by user mic
      Connecting to https://api.github.com using michaelneale/******
      Cloning the remote Git repository
      Cloning repository https://github.com/kzantow/failure-project.git
       ...
      [Pipeline] node
      Running on master in /Users/michaelneale/projects/paas/blueocean-plugin/blueocean/work/workspace/keitha/michaelneale-blockscoped
      

      And on conclusion of the build, a warning (valid) is not seen in step output:

      Using the ‘stage’ step without a block argument is deprecated
      Entering stage Archive
      Proceeding
      

      Yet these warnings would also be useful.

        Attachments

          Issue Links

            Activity

            jamesdumay James Dumay created issue -
            jamesdumay James Dumay made changes -
            Field Original Value New Value
            Epic Link JENKINS-35759 [ 171771 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            michaelneale Michael Neale made changes -
            Summary Developer wants to see a message when execution is blocked waiting for a node Developer wants to see a message when execution is blocked waiting for a node or Jenkins is busy
            michaelneale Michael Neale made changes -
            Summary Developer wants to see a message when execution is blocked waiting for a node or Jenkins is busy Developer wants to see a message when Jenkins is busy eg: execution is blocked waiting for a node
            michaelneale Michael Neale made changes -
            Description *Problem*
            When a pipeline is waiting for a node we display a generic "Waiting for run to start" message.

            *What we want to see*
            We want to show an appropriate message when a Pipeline is waiting for a node "Waiting for a node labeled XYZ to become available"

            {code}
            node ('does not exist or busy') {
              sh 'echo hello world'
            }
            {code}

            !blocked.png|thumbnail!
            *Problem*
            When Jenkins is working, for example waiting for a node, a user is given no feedback as to what is happening. Currently this is a generic "waiting for run to start" message.
            This is not captured in any steps logs currently.

            *What we want to see*
            We want to show an appropriate message when a Pipeline is waiting for a node "Waiting for a node labeled XYZ to become available"


            *Examples*
            For example with a simple pipeline:
            {code}
            node ('does not exist or busy') {
              sh 'echo hello world'
            }
            {code}

            which currently looks like:

            !blocked.png|thumbnail!

            In classic console it shows:
            {noformat}
            Started by user mic
            [Pipeline] node
            Still waiting to schedule task
            Waiting for next available executor
            {noformat}

            Ideally we can surface this information (who started it) but also that it is waiting for an executor, but also what the label expression/other deatils are.

            This should happen anywhere a node is requested (as one example) not just at the start of a build (so not an empty state).
            This could surface as a flownode which could be shown similar to a step (a synthetic step?)


            Another example:

            kzantow/failure-broject - branch name "michaelneale-blockscoped" when running that, the following information is omitted which could be useful:

            {noformat}
            Started by user mic
            Connecting to https://api.github.com using michaelneale/******
            Cloning the remote Git repository
            Cloning repository https://github.com/kzantow/failure-project.git
             ...
            [Pipeline] node
            Running on master in /Users/michaelneale/projects/paas/blueocean-plugin/blueocean/work/workspace/keitha/michaelneale-blockscoped
            {noformat}

            And on conclusion of the build, a warning (valid) is not seen in step output:

            {noformat}
            Using the ‘stage’ step without a block argument is deprecated
            Entering stage Archive
            Proceeding
            {noformat}

            Yet these warnings would also be useful.




            michaelneale Michael Neale made changes -
            Description *Problem*
            When Jenkins is working, for example waiting for a node, a user is given no feedback as to what is happening. Currently this is a generic "waiting for run to start" message.
            This is not captured in any steps logs currently.

            *What we want to see*
            We want to show an appropriate message when a Pipeline is waiting for a node "Waiting for a node labeled XYZ to become available"


            *Examples*
            For example with a simple pipeline:
            {code}
            node ('does not exist or busy') {
              sh 'echo hello world'
            }
            {code}

            which currently looks like:

            !blocked.png|thumbnail!

            In classic console it shows:
            {noformat}
            Started by user mic
            [Pipeline] node
            Still waiting to schedule task
            Waiting for next available executor
            {noformat}

            Ideally we can surface this information (who started it) but also that it is waiting for an executor, but also what the label expression/other deatils are.

            This should happen anywhere a node is requested (as one example) not just at the start of a build (so not an empty state).
            This could surface as a flownode which could be shown similar to a step (a synthetic step?)


            Another example:

            kzantow/failure-broject - branch name "michaelneale-blockscoped" when running that, the following information is omitted which could be useful:

            {noformat}
            Started by user mic
            Connecting to https://api.github.com using michaelneale/******
            Cloning the remote Git repository
            Cloning repository https://github.com/kzantow/failure-project.git
             ...
            [Pipeline] node
            Running on master in /Users/michaelneale/projects/paas/blueocean-plugin/blueocean/work/workspace/keitha/michaelneale-blockscoped
            {noformat}

            And on conclusion of the build, a warning (valid) is not seen in step output:

            {noformat}
            Using the ‘stage’ step without a block argument is deprecated
            Entering stage Archive
            Proceeding
            {noformat}

            Yet these warnings would also be useful.




            *Problem*
            When Jenkins is working, for example waiting for a node, a user is given no feedback as to what is happening. Currently this is a generic "waiting for run to start" message.
            This is not captured in any steps logs currently.

            *What we want to see*
            We want to show an appropriate message when a Pipeline is waiting for a node "Waiting for a node labeled XYZ to become available", and any other missing information that is not currently surfaces in step logs.


            *Examples*
            For example with a simple pipeline:
            {code}
            node ('does not exist or busy') {
              sh 'echo hello world'
            }
            {code}

            which currently looks like:

            !blocked.png|thumbnail!

            In classic console it shows:
            {noformat}
            Started by user mic
            [Pipeline] node
            Still waiting to schedule task
            Waiting for next available executor
            {noformat}

            Ideally we can surface this information (who started it) but also that it is waiting for an executor, but also what the label expression/other deatils are.

            This should happen anywhere a node is requested (as one example) not just at the start of a build (so not an empty state).
            This could surface as a flownode which could be shown similar to a step (a synthetic step?)


            Another example:

            kzantow/failure-broject - branch name "michaelneale-blockscoped" when running that, the following information is omitted which could be useful:

            {noformat}
            Started by user mic
            Connecting to https://api.github.com using michaelneale/******
            Cloning the remote Git repository
            Cloning repository https://github.com/kzantow/failure-project.git
             ...
            [Pipeline] node
            Running on master in /Users/michaelneale/projects/paas/blueocean-plugin/blueocean/work/workspace/keitha/michaelneale-blockscoped
            {noformat}

            And on conclusion of the build, a warning (valid) is not seen in step output:

            {noformat}
            Using the ‘stage’ step without a block argument is deprecated
            Entering stage Archive
            Proceeding
            {noformat}

            Yet these warnings would also be useful.




            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-38754 [ JENKINS-38754 ]
            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-38754 [ JENKINS-38754 ]
            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-38759 [ JENKINS-38759 ]
            jamesdumay James Dumay made changes -
            Assignee Vivek Pandey [ vivek ]
            jamesdumay James Dumay made changes -
            Sprint kraken [ 166 ] frank [ 156 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Sprint frank [ 156 ] frank, christmas [ 156, 176 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            hrmpw Patrick Wolf made changes -
            Link This issue is related to JENKINS-35905 [ JENKINS-35905 ]
            vivek Vivek Pandey made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            jamesdumay James Dumay made changes -
            Link This issue duplicates JENKINS-39647 [ JENKINS-39647 ]
            jamesdumay James Dumay made changes -
            Status In Progress [ 3 ] Resolved [ 5 ]
            Resolution Duplicate [ 3 ]
            jamesdumay James Dumay made changes -
            Resolution Duplicate [ 3 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            jamesdumay James Dumay made changes -
            Link This issue duplicates JENKINS-39647 [ JENKINS-39647 ]
            jamesdumay James Dumay made changes -
            Status Reopened [ 4 ] In Progress [ 3 ]
            jamesdumay James Dumay made changes -
            Sprint frank, christmas [ 156, 176 ] frank, tethys, christmas [ 156, 161, 176 ]
            jamesdumay James Dumay made changes -
            Link This issue depends on JENKINS-40856 [ JENKINS-40856 ]
            vivek Vivek Pandey made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            vivek Vivek Pandey made changes -
            Status In Review [ 10005 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            vivek Vivek Pandey made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            vivek Vivek Pandey made changes -
            Status Reopened [ 4 ] In Progress [ 3 ]
            michaelneale Michael Neale made changes -
            Assignee Vivek Pandey [ vivek ] Michael Neale [ michaelneale ]
            vivek Vivek Pandey made changes -
            Assignee Michael Neale [ michaelneale ] Vivek Pandey [ vivek ]
            vivek Vivek Pandey made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            jamesdumay James Dumay made changes -
            Sprint frank, tethys, christmas [ 156, 161, 176 ] frank, tethys, christmas, pannonian [ 156, 161, 176, 211 ]
            vivek Vivek Pandey made changes -
            Status In Review [ 10005 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            emanuelez emanuelez made changes -
            Status Resolved [ 5 ] In Review [ 10005 ]
            emanuelez emanuelez made changes -
            Status In Review [ 10005 ] Resolved [ 5 ]
            jamesdumay James Dumay made changes -
            Remote Link This issue links to "CloudBees Internal UX-600 (Web Link)" [ 18205 ]

              People

              • Assignee:
                vivek Vivek Pandey
                Reporter:
                jamesdumay James Dumay
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: