-
Bug
-
Resolution: Fixed
-
Major
-
-
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.
- blocks
-
JENKINS-26056 Workflow build step for Ant
-
- Resolved
-
- depends on
-
JENKINS-30383 SynchronousNonBlockingStepExecution should allow restart of idempotent steps
-
- Resolved
-
- relates to
-
JENKINS-49337 GeneralNonBlockingStepExecution (was: InterruptedException from step tail call)
-
- Closed
-
-
JENKINS-26055 DurableTaskStep
-
- Resolved
-
-
JENKINS-32986 hard killing a pipeline leaves the JVM CPS thread running.
-
- Open
-
-
JENKINS-35420 Realtime junit report to support Pipeline (was: throws ClassCastException when pipeline run)
-
- Resolved
-
-
JENKINS-42561 Users should be able to custom configure the timeout on pipeline build wrappers/steps
-
- Resolved
-
- links to
[JENKINS-43276] CoreWrapperStep should run SimpleBuildWrapper.setUp asynchronously
Link |
New:
This issue depends on |
Link | New: This issue relates to JENKINS-32986 [ JENKINS-32986 ] |
Link |
New:
This issue relates to |
Link |
New:
This issue relates to |
Link |
New:
This issue blocks |
Link |
New:
This issue relates to |
Labels | Original: performance threads | New: performance threads triaged-2018-11 |
JENKINS-26055(orJENKINS-37011) would make it easier to write a regular Step which as part of its functionality launches an external process with an unknown run duration.