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

Hide flyweight master executor when ≥1 heavyweight executors running as subtasks

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • pipeline

      If you have

      node {
        sh 'sleep 60'
      }
      

      it would be nice if the flyweight executor were hidden from the executor widget.

          [JENKINS-26900] Hide flyweight master executor when ≥1 heavyweight executors running as subtasks

          Jesse Glick created issue -

          From the other side, if we have the flow idle on user input we still need to see that.

          Yuriy Kryshchuk added a comment - From the other side, if we have the flow idle on user input we still need to see that.

          Jesse Glick added a comment -

          if we have the flow idle on user input we still need to see that

          Well you would always see at least one task for a running build in the executor widget, from which you can access the input page. (The build history widget shown on the flow’s index page is not affected either.) This is just intended to make simple one-slave flows show only one entry.

          Jesse Glick added a comment - if we have the flow idle on user input we still need to see that Well you would always see at least one task for a running build in the executor widget, from which you can access the input page. (The build history widget shown on the flow’s index page is not affected either.) This is just intended to make simple one-slave flows show only one entry.

          Jesse Glick added a comment -

          Unfortunately it seems this needs a core API extension, since lib/hudson/executors.jelly does not offer a Queue.Executable a choice of whether it should display a table row, so it does not suffice for WorkflowRun/executorCell.jelly to be an empty <td/>.

          Jesse Glick added a comment - Unfortunately it seems this needs a core API extension, since lib/hudson/executors.jelly does not offer a Queue.Executable a choice of whether it should display a table row, so it does not suffice for WorkflowRun/executorCell.jelly to be an empty <td/> .
          Jesse Glick made changes -
          Labels New: api

          Jesse Glick added a comment -

          JENKINS-25938 also requires an extension to the Executable API.

          Jesse Glick added a comment - JENKINS-25938 also requires an extension to the Executable API.
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-25938 [ JENKINS-25938 ]

          Daniel Beck added a comment -

          Is it possible for the flyweight executor of Workflows to be on a non-master slave node different from whatever happens inside the workflow? If so, what happens when you take that node offline?

          Daniel Beck added a comment - Is it possible for the flyweight executor of Workflows to be on a non-master slave node different from whatever happens inside the workflow? If so, what happens when you take that node offline?

          Jesse Glick added a comment -

          No, the flyweight executor is always on master.

          Really what I want is for this executor to appear iff the CPS VM thread is currently busy, which is closely related to JENKINS-22941.

          Jesse Glick added a comment - No, the flyweight executor is always on master. Really what I want is for this executor to appear iff the CPS VM thread is currently busy, which is closely related to JENKINS-22941 .
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-22941 [ JENKINS-22941 ]

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: