Hi I have a simple job running
java -version killall python || true python -m SimpleHTTPServer 9999 & but the python job is still running after the job run has ended. Sys info: https://gist.github.com/andreineculau/10965094 On IRC #jenkins, I learned last night that the ProcessTreeKiller feature is not intended for spawned processes from an Execute Shell build step. *Can someone confirm that?* I'm asking because looking at several online answers, the feature SHOULD kill those spawned processes as well (my assumption as well). http://stackoverflow.com/questions/16667898/start-daemon-on-remote-server-via-jenkins-ssh-shell-script-exits-mysteriously https://groups.google.com/forum/m/#!topic/jenkinsci-users/SYl9s7WCh-c https://groups.google.com/forum/?nomobile=true#!searchin/jenkinsci-users/processtreekiller/jenkinsci-users/rx6oFgbcqiM/SFe5zdUBkE0J https://groups.google.com/forum/?nomobile=true#!searchin/jenkinsci-users/processtreekiller/jenkinsci-users/x7i1FbJNR88/OJ2vh3Cli78J ... +larrys │23:47:28 andrei | [diecast]: no. i am putting that process in the background: python -m SimpleHTTPServer 8080 & +lifeless │23:48:00 [diecast] | that's not really the way to do that +orrc │23:48:10 [diecast] | and it should still be running +recampbell │23:48:12 ojacobson | andrei: so the shell continues immediately, with python as a child process. Then the shell exits. +rpetti │23:48:19 [diecast] | you have to explicitly kill it +schristou │23:48:52 [diecast] | what do you want to do eventually +Slide-O-Mix │23:48:55 [diecast] | maybe we can help +stephenc │23:48:59 andrei | [diecast]: ahm. so i am in the wrong here and jenkins is not supposed to kill any processes that share some characteristic env vars? [diecast] │23:49:13 [diecast] | it only does what it is told =) [q0rban] │23:49:22 andrei | ref: https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller [reed] │23:49:58 [diecast] | it does that _eitoball │23:50:05 [diecast] | it kills the build step exec shell afex │23:50:18 @kohsuke | If I have all the sponsor talks in one track would that be too evil? Alan_S │23:50:50 andrei | my goal: make sure that when a job run ends there are no processes started by the build step exec shell that are left running AlexejK │23:51:30 [diecast] | jenkins is not aware of processes spawned outside of jenkins alexwhitman │23:51:57 [diecast] | once you background a process it is on its own alyssa │23:52:29 [diecast] | write a pid -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
