Details

Description

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.

Attachments

Issue Links

is blocked by

JENKINS-37121WorkspaceListLeasePickle should help diagnose locked workspaces

Activity

Implementation complete, except for the last suggestion to automatically abort an ExecutorPickle which is determined to be unloadable due to a deleted ephemeral node. This could be done later if desired. In the meantime, it is now much easier to identify and cancel builds affected by such issues.

Jesse Glick
added a comment - 2016-06-10 19:12 Implementation complete, except for the last suggestion to automatically abort an ExecutorPickle which is determined to be unloadable due to a deleted ephemeral node. This could be done later if desired. In the meantime, it is now much easier to identify and cancel builds affected by such issues.