[
https://issues.jenkins-ci.org/browse/JENKINS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158732#comment-158732
]
m_broida edited comment on JENKINS-3105 at 2/7/12 5:43 PM:
-----------------------------------------------------------
Details on this workaround work, please?
Does it prevent intentionally killing/aborting a build?
Can a build step in the job just set a BUILD_ID envvar?
Is the specific value "dontKillMe" required, or will any value work?
Adding a parameter to every one of our many jobs (and new ones) would be a
hassle, even if users could accept a default value.
Can the BUILD_ID envvar be set in the overall Jenkins configuration to affect
all Jenkins jobs?
Can the BUILD_ID envvar be set at the OS level to affect all Jenkins jobs?
We have had to restrict many of our jobs to run on nodes with only a single
executor to ensure that the situation doesn't arise. A real fix would be most
helpful.
was (Author: m_broida):
Details on this workaround work, please?
Can a build step in the job just set a BUILD_ID envvar?
Is the specific value "dontKillMe" required, or will any value work?
Adding a parameter to every one of our many jobs (and new ones) would be a
hassle, even if users could accept a default value.
Can the BUILD_ID envvar be set in the overall Jenkins configuration to affect
all Jenkins jobs?
Can the BUILD_ID envvar be set at the OS level to affect all Jenkins jobs?
We have had to restrict many of our jobs to run on nodes with only a single
executor to ensure that the situation doesn't arise. A real fix would be most
helpful.
> Configuration UI to disable process tree killer selectively
> -----------------------------------------------------------
>
> Key: JENKINS-3105
> URL: https://issues.jenkins-ci.org/browse/JENKINS-3105
> Project: Jenkins
> Issue Type: Improvement
> Components: other
> Affects Versions: current
> Environment: Platform: Sun, OS: Solaris
> Reporter: olamy
> Priority: Trivial
>
> Due to fix https://hudson.dev.java.net/issues/show_bug.cgi?id=2729, I can't
> restart my tomcat instance with using a script which worked fine before 1.283.
> My script called fastRestart.sh is :
> PWD=`pwd`
> cd $PWD
> #BUILD_ID="dontKillMe catalina.sh start"
> #BUILD_ID="dontKillMe ./startup.sh"
> echo $BUILD_ID
> kill -9 `cat ./tomcat.pid` && ./startup.sh
> My hudson job do :
> BUILD_ID=dontKillMe startup.sh && cd
> /local/dotw/tomcat-dev-ota-ah/apache-tomcat-6.0.14/bin && ./fastRestart.sh
> job console output :
> started
> [workspace] $ /bin/sh -xe
> /local/dotw/tmp/hudson-tmp/hudson3776950102996593394.sh
> BUILD_ID=dontKillMe startup.sh
> + cd /local/dotw/tomcat-dev-ota-ah/apache-tomcat-6.0.14/bin
> + ./fastRestart.sh
> + pwd
> PWD=/local/dotw/tomcat-dev-ota-ah/apache-tomcat-6.0.14/bin
> + cd /local/dotw/tomcat-dev-ota-ah/apache-tomcat-6.0.14/bin
> + echo dontKillMe startup.sh
> dontKillMe startup.sh
> + cat ./tomcat.pid
> + kill -9 9822
> + ./startup.sh
> finished: SUCCESS
> Here the tomcat has been killed and restarted but immediatly stop due to fix
> for
> 2729.
> Is there any other workaround ?
> IMHO we should have a flag when running a script which "don't kill child
> processes" (to preserve a minimum of backward compatibility and a minimum of
> some jobs/scripts rewriting)
> Thanks
> --
> Olivier
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
