[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
SCM/JIRA link daemon commented on JENKINS-22249 Record process ID of spawned process Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/workflow-plugin/7f63d35b76eeb7140c4807af0209d2380bc65a54 Log: durable-task 0.7 to pick up reworked JENKINS-22249 fix. Compare: https://github.com/jenkinsci/workflow-plugin/compare/a3f94a7e0296...7f63d35b76ee 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
SCM/JIRA link daemon commented on JENKINS-22249 Record process ID of spawned process Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java http://jenkins-ci.org/commit/durable-task-plugin/88aed023e5d37fdae0d1e0c05acd7cabbdf6fd7f Log: JENKINS-22249 Do not bother checking process existence if we just started it. 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
SCM/JIRA link daemon commented on JENKINS-22249 Record process ID of spawned process Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java src/main/java/org/jenkinsci/plugins/durabletask/ProcessLiveness.java http://jenkins-ci.org/commit/durable-task-plugin/d75ffad16c40c0018fd6e71499f6b6e96048798f Log: [FIXED JENKINS-22249] Rewrote ProcessLiveness to use a simple [ -d /proc/$pid ] check. 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
SCM/JIRA link daemon resolved JENKINS-22249 as Fixed Record process ID of spawned process Change By: SCM/JIRA link daemon (10/Oct/14 4:37 AM) Status: In Progress Resolved Resolution: Fixed 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
Jesse Glick updated JENKINS-22249 Record process ID of spawned process Change By: Jesse Glick (10/Oct/14 4:21 AM) Status: Reopened Open 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
Jesse Glick started work on JENKINS-22249 Record process ID of spawned process Change By: Jesse Glick (10/Oct/14 4:21 AM) Status: Open In Progress 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
Jesse Glick reopened JENKINS-22249 Record process ID of spawned process Using a cached ProcessTree does not seem reliable, and was probably inefficient anyway. Change By: Jesse Glick (10/Oct/14 3:44 AM) Resolution: Fixed Status: Resolved Reopened 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
SCM/JIRA link daemon resolved JENKINS-22249 as Fixed Record process ID of spawned process Change By: SCM/JIRA link daemon (08/Oct/14 7:17 PM) Status: In Progress Resolved Resolution: Fixed 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
SCM/JIRA link daemon commented on JENKINS-22249 Record process ID of spawned process Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java src/main/java/org/jenkinsci/plugins/durabletask/FileMonitoringTask.java src/main/java/org/jenkinsci/plugins/durabletask/ProcessLiveness.java http://jenkins-ci.org/commit/durable-task-plugin/41a11fb64845238e641fb005bb6bb7226407402d Log: [FIXED JENKINS-22249] Detect if the wrapper shell script is dead, for example because the machine was rebooted. 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
Jesse Glick edited a comment on JENKINS-22249 Record process ID of spawned process Filed JENKINS-25053 for Windows. 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
Jesse Glick started work on JENKINS-22249 Record process ID of spawned process Change By: Jesse Glick (08/Oct/14 6:11 PM) Status: Open In Progress 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
Jesse Glick commented on JENKINS-22249 Record process ID of spawned process http://serverfault.com/questions/126502/how-to-get-own-process-pid-from-the-command-prompt-in-windows/126643#126643 is the only thing I can find for Windows. Ugly! 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.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
Jesse Glick created JENKINS-22249 Record process ID of spawned process Issue Type: Bug Assignee: Jesse Glick Components: durable-task Created: 18/Mar/14 5:34 PM Description: Currently BourneShellScript does not try to track the PID of the external process; it assumes that it runs to completion (successfully or not) and then writes the status file. But if the wrapping shell script is killed, or the machine rebooted, this might never occur and the task would hang. Better to record $$ from the outer sh process and override exitStatus in case no such process still exists. Implies some use of native code. (TBD whether an analogous fix can be done for Windows as well.) Project: Jenkins Priority: 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.
