There is a similar known issue that started to affect Jenkins in 1.553: https://issues.jenkins-ci.org/browse/JENKINS-22641
Are you absolutely sure it still worked on 1.556 for you? In your case, did you rely on process killing for successful builds only, but also for failed builds? On 16.05.2014, at 16:01, Jan Řezníček <ing.jan.rezni...@gmail.com> wrote: > I have just upgraded Jenkins from 1.556 to 1.563. > I have a job, that stats JBoss application server on my Linux slave node. > In 1.556, the java process with server was killed after the build was > finished. ProcessTreeKiller managed to kill all processes, that i started > during the build. > > But after the upgrade to version 1.563, the JBoss processes are not killed > after the build is finished. It caused me a lot of troubles. > I did not change any settings (disabling ProcessTree, asi is mention here: > https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller) > > Do you know something about that? Is this a bug, or expected behaviour? > > Thaks for reactions. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
