The problem that a process initiated by the Execute shell in Jenkins will be killed

When you configure the Automatic Updates deployment project in Jenkins, you can turn tomcat off if you take the Execute shell to start/close Tomcat,

However, Tomcat could not be started, although the build would show that the execution was successful, but the view process was not started by Tomcat. This is because the Jenkins default

Kill all the spawned processes after the build is finished. The following configuration is required to avoid this situation:

1. Reset the environment variable build_id

Adding Build_id=dontkillme to the Execute Shell input box prevents Jenkins from killing the started Tomcat process

 

2. Prohibit Jenkins from killing the derivative process when starting Jenkins

Modify the/etc/sysconfig/jenkins configuration to add-dhudson.util.processtree.disable=true to the jenkins_java_options.

Need to restart Jenkins to take effect

Once this method is configured, all jobs do not have to be set build_id to prevent Jenkins from killing the booted Tomcat process

<wiz_tmp_tag id= "Wiz-table-range-border" contenteditable= "false" style= "Display:none;" >

The problem that a process initiated by the Execute shell in Jenkins will be killed