-
Bug
-
Resolution: Fixed
-
Major
After restarting Jenkins with a running flow that has some "pickled" object references (such as slave/workspace pairs from the node step), the flow does not resume until all pickles are resolved. This delay could be long, and the user may have no idea what is happening, because nothing is shown in the console.
- is blocked by
-
JENKINS-37121 WorkspaceListLeasePickle should help diagnose locked workspaces
- Resolved
- is blocking
-
JENKINS-25890 Deadlock between RunMap and Queue after restart; StepContext.isReady impl acquires lock
- Resolved
-
JENKINS-36013 Automatically abort ExecutorPickle rehydration from an ephemeral node
- Closed
- is related to
-
JENKINS-25550 Hard kill
- Resolved
-
JENKINS-29705 Virtual thread dump
- Resolved
-
JENKINS-31842 Allow steps to decorate thread dumps
- Resolved
- links to