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
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/574C0717.1060905%40gmx.at.
For more options, visit https://groups.google.com/d/optout.
