[JIRA] [durable-task-plugin] (JENKINS-26105) Unkillable tasks

Tue, 16 Dec 2014 16:18:09 -0800

Issue Type: Bug Bug
Assignee: Jesse Glick
Components: durable-task-plugin
Created: 17/Dec/14 12:16 AM
Description:

If you run a flow

node {
    sh 'rm -rf * .*'
}

this deletes the control directory for the shell step while it is running, and it becomes impossible to abort the build.



I think this is because FileMonitoringController.exitStatus just checks if jenkins-result.txt exists yet. But if the whole control dir is missing, it should return -1 or similar.



Similar effect if you botch the $PATH so that echo cannot be found. In that case the control dir is present, but pid is not, so the controller assumes the process is still starting! It should impose a time limit on the startup phase.



Was ameliorated by improving DurableTaskExecution.stop to do a hard kill if you try to stop the build twice. This makes the similar JENKINS-25678 much less of a problem.
Project: Jenkins
Labels: workflow robustness
Priority: Major Major
Reporter: Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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.

Reply via email to