We use Hudson to start a Tomcat application server before tests are running. The freestyle project uses
an ant target for this with "fork=true" and "spawn=true", because we want to keep the Tomcat running
after the build.
Since Hudson version 1.284 it kills the tomcat-process after the build finished, even if the spawn
option is set.
Is there an option in Hudson available that prevents the process-killing?
Thank you
Timo Meinen
Description
We use Hudson to start a Tomcat application server before tests are running. The freestyle project uses
an ant target for this with "fork=true" and "spawn=true", because we want to keep the Tomcat running
after the build.
Since Hudson version 1.284 it kills the tomcat-process after the build finished, even if the spawn
option is set.
Is there an option in Hudson available that prevents the process-killing?
Thank you
Timo Meinen
mdonohue added a comment - 24/Feb/09 07:40 PM set the environment variable BUILD_ID to something like 'dontKillMe' in the
process that should stay alive.
Hudson looks for that environment variable when cleaning up stray processes.
This issue has been marked as a duplicate of 3105 ***
Bug
Resolved
Blocker
Hudson kills processes started within builds
set the environment variable BUILD_ID to something like 'dontKillMe' in the
process that should stay alive.
Hudson looks for that environment variable when cleaning up stray processes.