-
Bug
-
Resolution: Fixed
-
Critical
-
Jenkins 1.553 or later on CentOS 6.3 with Oracle Java 7 JDK
Starting at version 1.553, Jenkins no longer seems to kill running processes after a build failure.
We have several jobs that start a Tomcat instance and run various end-to-end-tests; if the build fails Jenkins doesn't execute the shutdown scripts and we rely on the process killer to clean up the Tomcat instance.
This can be duplicated more easily by creating a free-form job and adding two shell scripts, the first that starts a simple command such as "nohup sleep 10000 &" and the second "/bin/false". After the job exits the sleep process is still running. Prior to version 1.553, it would be killed.
There are no log messages to indicate a problem.
I can reproduce this on CentOS 6, Red Hat EL 5 and Red Hat EL 4, both with a job running on the local master, and on a slave node. Also tested with both 32-bit and 64-bit Oracle Java 7 JDKs.
We're using the built-in Winstone container.
- depends on
-
JENKINS-26048 Jenkins no longer cleaning up child processes when build stopped - as of 1.587
-
- Reopened
-
- is related to
-
JENKINS-28968 Aborting builds does not kill surefire sub-process
-
- Reopened
-
Integrated in
jenkins_main_trunk #3538
[FIXED JENKINS-22641] FileUtils.readFileToByteArray behavior has changed in the latest version of commons-io. (Revision 410f06adfa798d29118c77ed01c5c02fc207cb02)
Add test unit for
JENKINS-22641(Revision 0d4c0cb6b274bfa18c810fcf761e3ad8b27ceb34)JENKINS-22641Noting merge of #1322. (Revision 14a147eda8eebfd78c1cc53e1d59232d720de6b7)Result = SUCCESS
schristou88 : 410f06adfa798d29118c77ed01c5c02fc207cb02
Files :
schristou88 : 0d4c0cb6b274bfa18c810fcf761e3ad8b27ceb34
Files :
Jesse Glick : 14a147eda8eebfd78c1cc53e1d59232d720de6b7
Files :