Job Abort on Windows only kills child processes if jenkins-slave.exe ist running?
272 views
Skip to first unread message
Martin Ba
May 30, 2016, 5:26:03 AM5/30/16
to Jenkins Users
Ver: LTS Jenkins ver. 1.625.2
We run our Windows Build nodes/slaves via the Windows Service
jenkins-slave.exe
Sometimes the Windows Service process "goes down", but its java.exe
child process that is actually running the jenkins slave continues to
work (fine).
What we noticed with this is that when the service exe parent process is
down, aborting a Job doesn't kill the child processes of the job anymore:
Normally, aborting a job will kill all child processes of the current
build step on the slave. With no service running, only the immediate
build step (batch: cmd.exe) is terminated, but its running child
processes just continue.
Is this a known problem? Mitigation?
cheers,
Martin
We run our Windows Build nodes/slaves via the Windows Service
jenkins-slave.exe
Sometimes the Windows Service process "goes down", but its java.exe
child process that is actually running the jenkins slave continues to
work (fine).
What we noticed with this is that when the service exe parent process is
down, aborting a Job doesn't kill the child processes of the job anymore:
Normally, aborting a job will kill all child processes of the current
build step on the slave. With no service running, only the immediate
build step (batch: cmd.exe) is terminated, but its running child
processes just continue.
Is this a known problem? Mitigation?
cheers,
Martin
Reply all
Reply to author
Forward
0 new messages