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

Strengthen SynchronousNonBlockingStepExecution.getStatus

      getStatus just reports a threadName. It should also indicate whether task had been created, and whether it is considered cancelled or done.

      In principle a call to stop after start but before the task starts running could result in a hung step. This would normally be a very short interval, though, since the thread pool is unbounded. Could be made more robust.

          [JENKINS-39386] Strengthen SynchronousNonBlockingStepExecution.getStatus

          Jesse Glick created issue -
          Jesse Glick made changes -
          Epic Link New: JENKINS-35396 [ 171189 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-30383 [ JENKINS-30383 ]
          Jesse Glick made changes -
          Summary Original: Strengthen AbstractSynchronousNonBlockingStepExecution.getStatus New: Strengthen SynchronousNonBlockingStepExecution.getStatus
          CloudBees Inc. made changes -
          Remote Link New: This issue links to "CloudBees Internal OSS-1614 (Web Link)" [ 18626 ]
          Marky Jackson made changes -
          Epic Link Original: JENKINS-35396 [ 171189 ]

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

              Created:
              Updated: