I have tried the following conditions:
1. *Master*: CentOS release 6.8 (Final) *Slave*: Red Hat Enterprise
Linux Server release 6.4 (Santiago) *Result*: Not Be Killed
2. *Master*: Red Hat Enterprise Linux Server release 5.6 (Tikanga)
*Slave*: Red Hat Enterprise Linux Server release 6.4 (Santiago) *Result*:
Not Be Killed
3. *⭐Master*: Red Hat Enterprise Linux Server release 6.4 (Santiago)
*Slave*: Red Hat Enterprise Linux Server release 6.4 (Santiago) *Result*
: *Be Killed*
Why Background processes be killed WHEN THE MASTER OS IS RH6.4?
IS THIS A BUG OR SYSTEM SETTING ERROR?
*Experimental data:*
Under normal condition, TOMCAT process will keep alive in the background.
BUT, using RH6.4 as jenkins master, TOMCAT process will be killed !
Code in Pipeline :
> stage('Startup'){
>
> node('_your_node_'){
>
> timestamps {
>
> def exec = '''
>
> BUILD_ID=dontKillMe ./call.sh
>
> sleep 20
>
> '''
>
> sh exec
>
> }
>
> }
>
> }
>
>
call.sh :
> #!/bin/sh
>
> . ~/.bash_profile
>
> ${TOMCAT_HOME}/bin/startup.sh
>
>
Jenkins Version: 2.32.3 / 2.60.1
JAVA Version: 1.8.0_121
TOMCAT Version(for jenkins): 9.0.0.M17
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/587c45e3-2e70-4016-b459-dad684081744%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
