[JIRA] (JENKINS-36013) Automatically abort ExecutorPickle rehydration from an ephemeral node
Title: Message Title Patrick Wolf commented on JENKINS-36013 Re: Automatically abort ExecutorPickle rehydration from an ephemeral node Sounds related to what R. Tyler Croy is experiencing with JENKINS-41569. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36013) Automatically abort ExecutorPickle rehydration from an ephemeral node
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36013 Automatically abort ExecutorPickle rehydration from an ephemeral node Change By: Jesse Glick Component/s: workflow-durable-task-step-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36013) Automatically abort ExecutorPickle rehydration from an ephemeral node
Title: Message Title Jesse Glick commented on JENKINS-36013 Re: Automatically abort ExecutorPickle rehydration from an ephemeral node Originally suggested in JENKINS-26130 but I felt it was better to split this out. JENKINS-26130 does at least provide a much more comprehensible diagnosis for the problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36013) Automatically abort ExecutorPickle rehydration from an ephemeral node
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-36013 Automatically abort ExecutorPickle rehydration from an ephemeral node Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Jun/16 2:12 PM Labels: robustness Priority: Major Reporter: Jesse Glick ExecutorPickle.rehydrate ought to be able to detect that it has been spinning in circles because the agent node it was supposed to run on is not in the Jenkins node list, and automatically abort, causing the build to fail with a comprehensible message rather than just hanging indefinitely. (As opposed to being registered but offline, which is normal enough for a JNLP agent etc.—in such cases we just want to wait for the agent to come back online.) This would provide a better experience for the case of a build which was running on an EphemeralNode (such as from a Cloud without durable-task integration) when Jenkins was restarted. An agent using an inappropriate RetentionStrategy is trickier since it might still be defined after a restart, but will soon be terminated. Similarly, there may be cases where the agent is actually going to be redefined (with the same name) when it is attached after the restart—not sure about the Swarm plugin, but CloudBees DEV@cloud OPEs work this way. To prevent the build from being killed too aggressively, the cleanup should be delayed until some time has elapsed since rehydration began (or, ideally, since Jenkins completed initialization)—say, five minutes.
