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

Cause Description is not displayed when mousing over a part of a pipeline item in the queue.

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core, pipeline

      Expected Behavior:

      When you hover your mouse over an item in the queue, you expect to see the build cause description appear (e.g. "Started by SCM change" or "commit notification xyz" or "started by user").

      Observed Behavior:

      When a queued item has been scheduled by a pipeline, only its node label will appear when you hover over it. The cause description for that item will not.

      This makes it difficult to track down an item in the queue that corresponds to a specific commit or user.

       

      Using the script console, I queried this item in the queue, and saw that it had a cause description saying "commit notification xyz..." - however, that notification does not appear here in the Jenkins queue UI when you mouse over the item.

       

      This item was created by using a simple Jenkins Pipeline job that has one node and some empty stages. What you see in the queue image above is the pipeline waiting for one of the specified executors to become available.

      This problem also appears when you create several nodes in parallel using the parallel() directive.

       

          [JENKINS-45890] Cause Description is not displayed when mousing over a part of a pipeline item in the queue.

          Jack Zylkin created issue -
          Jack Zylkin made changes -
          Description Original: When you hover your mouse over an item in the queue, you expect to see the build cause description appear (e.g. "Started by SCM change" or "commit notification xyz" or "started by user").  When the item has been scheduled by a pipeline, only the node label will appear. The cause descriptions will not.

          This makes it difficult to track down an item in the queue that corresponds to a specific commit or user.

           

          !image-2017-07-31-17-33-48-307.png!

          Using the script console, I queried this item in the queue, and saw that it had a cause description saying "commit notification xyz..." - however, that notification does not appear here in the Jenkins queue UI when you mouse over the item.

           

          This item was created by using a Jenkins Pipeline job, which appears here in the queue because it is waiting for one of the specified nodes to become available.

          This problem also appears when you create several nodes in parallel using the parallel() directive.

           
          New: *Expected Behavior:*

          When you hover your mouse over an item in the queue, you expect to see the build cause description appear (e.g. "Started by SCM change" or "commit notification xyz" or "started by user"). 

          *Observed Behavior:*

          When a queued item has been scheduled by a pipeline, only its node label will appear when you hover over it. The cause description for that item will not.

          This makes it difficult to track down an item in the queue that corresponds to a specific commit or user.

           

          !image-2017-07-31-17-33-48-307.png!

          Using the script console, I queried this item in the queue, and saw that it had a cause description saying "commit notification xyz..." - however, that notification does not appear here in the Jenkins queue UI when you mouse over the item.

           

          This item was created by using a Jenkins Pipeline job, which appears here in the queue because it is waiting for one of the specified nodes to become available.

          This problem also appears when you create several nodes in parallel using the parallel() directive.

           
          Jack Zylkin made changes -
          Description Original: *Expected Behavior:*

          When you hover your mouse over an item in the queue, you expect to see the build cause description appear (e.g. "Started by SCM change" or "commit notification xyz" or "started by user"). 

          *Observed Behavior:*

          When a queued item has been scheduled by a pipeline, only its node label will appear when you hover over it. The cause description for that item will not.

          This makes it difficult to track down an item in the queue that corresponds to a specific commit or user.

           

          !image-2017-07-31-17-33-48-307.png!

          Using the script console, I queried this item in the queue, and saw that it had a cause description saying "commit notification xyz..." - however, that notification does not appear here in the Jenkins queue UI when you mouse over the item.

           

          This item was created by using a Jenkins Pipeline job, which appears here in the queue because it is waiting for one of the specified nodes to become available.

          This problem also appears when you create several nodes in parallel using the parallel() directive.

           
          New: *Expected Behavior:*

          When you hover your mouse over an item in the queue, you expect to see the build cause description appear (e.g. "Started by SCM change" or "commit notification xyz" or "started by user").

          *Observed Behavior:*

          When a queued item has been scheduled by a pipeline, only its node label will appear when you hover over it. The cause description for that item will not.

          This makes it difficult to track down an item in the queue that corresponds to a specific commit or user.

           

          !image-2017-07-31-17-33-48-307.png!

          Using the script console, I queried this item in the queue, and saw that it had a cause description saying "commit notification xyz..." - however, that notification does not appear here in the Jenkins queue UI when you mouse over the item.

           

          This item was created by using a Jenkins Pipeline job, which appears here in the queue because it is waiting for one of the specified nodes to become available.

          This problem also appears when you create several nodes in parallel using the parallel() directive.

           
          Jack Zylkin made changes -
          Description Original: *Expected Behavior:*

          When you hover your mouse over an item in the queue, you expect to see the build cause description appear (e.g. "Started by SCM change" or "commit notification xyz" or "started by user").

          *Observed Behavior:*

          When a queued item has been scheduled by a pipeline, only its node label will appear when you hover over it. The cause description for that item will not.

          This makes it difficult to track down an item in the queue that corresponds to a specific commit or user.

           

          !image-2017-07-31-17-33-48-307.png!

          Using the script console, I queried this item in the queue, and saw that it had a cause description saying "commit notification xyz..." - however, that notification does not appear here in the Jenkins queue UI when you mouse over the item.

           

          This item was created by using a Jenkins Pipeline job, which appears here in the queue because it is waiting for one of the specified nodes to become available.

          This problem also appears when you create several nodes in parallel using the parallel() directive.

           
          New: *Expected Behavior:*

          When you hover your mouse over an item in the queue, you expect to see the build cause description appear (e.g. "Started by SCM change" or "commit notification xyz" or "started by user").

          *Observed Behavior:*

          When a queued item has been scheduled by a pipeline, only its node label will appear when you hover over it. The cause description for that item will not.

          This makes it difficult to track down an item in the queue that corresponds to a specific commit or user.

           

          !image-2017-07-31-17-33-48-307.png!

          Using the script console, I queried this item in the queue, and saw that it had a cause description saying "commit notification xyz..." - however, that notification does not appear here in the Jenkins queue UI when you mouse over the item.

           

          This item was created by using a simple Jenkins Pipeline job that has one node and some empty stages. What you see in the queue image above is the pipeline waiting for one of the specified executors to become available.

          This problem also appears when you create several nodes in parallel using the parallel() directive.

           
          Oleg Nenashev made changes -
          Component/s New: pipeline [ 21692 ]
          Vivek Pandey made changes -
          Labels Original: Queue New: Queue triaged-2018-11

            Unassigned Unassigned
            jzylkin Jack Zylkin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: