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

CoreWrapperStep should run SimpleBuildWrapper.setUp asynchronously

    • workflow-basic-steps 2.14

      CoreStep runs SimpleBuildStep.perform in a background thread, via SynchronousNonBlockingStepExecution, so while pending JENKINS-30383 there is a high chance that a Jenkins restart will cause a build failure, at least the CPS VM thread is not blocked. However CoreWrapperStep runs SimpleBuildWrapper.setUp directly from Execution.start, since there is no block-scoped equivalent of SynchronousNonBlockingStepExecution, which means that a slow wrapper could block the VM thread indefinitely.

          [JENKINS-43276] CoreWrapperStep should run SimpleBuildWrapper.setUp asynchronously

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue depends on JENKINS-30383 [ JENKINS-30383 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-32986 [ JENKINS-32986 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-42561 [ JENKINS-42561 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-26055 [ JENKINS-26055 ]
          Jesse Glick made changes -
          Link New: This issue blocks JENKINS-26056 [ JENKINS-26056 ]
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-35420 [ JENKINS-35420 ]
          Vivek Pandey made changes -
          Labels Original: performance threads New: performance threads triaged-2018-11
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-49337 [ JENKINS-49337 ]
          Jesse Glick made changes -
          Assignee New: Jesse Glick [ jglick ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

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

              Created:
              Updated:
              Resolved: