-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Linux
Jenkins 2.60.2
The latest Pipeline plug-ins as of 2017-07-09
After one of the recent updates to pipeline plug-ins the process tree killer always kills all processes even if the BUILD_ID (as described in https://wiki.jenkins.io/display/JENKINS/ProcessTreeKiller) is changed. This is a serious regression because some of our build jobs stopped working.
The following pipeline script can be used to reproduce the problem:
node('master') { sh '''BUILD_ID="dont-kill-me bla/blub" sleep 60 &''' }
The sleep process is killed immediately when the job finishes. The problem only occurs in Pipeline jobs, freestyle jobs still work as expected, i.e. the sleep process continues running for 60 seconds.
- relates to
-
JENKINS-28182 Revisit use of $JENKINS_SERVER_COOKIE and Launcher.kill
-
- Resolved
-
Hi Thorsten,
This is Pipeline working as designed – what you're describing would permit the Pipeline to leak processes potentially due to how it's launching them with the shell step. IIUC what you're saying, the fact that it doesn't kill the process in FreeStyle projects would be a bug with Freestyle.