-
Bug
-
Resolution: Fixed
-
Major
-
None
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.)
- depends on
-
JENKINS-25727 Occasional exit status -1 with long latencies
- Resolved
-
JENKINS-32264 sh step returns ERROR -1, but shell step still running
- Resolved
- is related to
-
JENKINS-25053 Record process ID of spawned process on Windows
- Open