Currently WorkflowRun.waitForCompletion spins on a thread just so it can hold a (flyweight) Executor open. Similarly, ExecutorStepExecution.PlaceholderTask spins just to hold a (heavyweight) Executor open. These are wasteful. There should be an optional Task or Executable interface that can run asynchronously, without literally consuming a native Thread for each one.

          [JENKINS-25938] Lock an Executor without creating a Thread

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue is duplicated by JENKINS-26098 [ JENKINS-26098 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-26900 [ JENKINS-26900 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-22941 [ JENKINS-22941 ]
          Jesse Glick made changes -
          Assignee New: Jesse Glick [ jglick ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "PR 1610 (Web Link)" [ 12169 ]
          Jesse Glick made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Ireneusz Makowski made changes -
          Labels Original: api executor performance threads workflow New: api executor lts-candidate performance threads workflow
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-28182 [ JENKINS-28182 ]
          Daniel Beck made changes -
          Labels Original: api executor lts-candidate performance threads workflow New: api executor performance threads workflow

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: