title: How to tell jenkins not to kill processes after successful execution of job in multijob project?
body: <p>I have a jenkins <strong>multijob project</strong>.</p>
  
  <p><strong>In 1st phase</strong>, I start databases and build core part.</p>
  
  <p>sample shell command to start Mongodb:</p>
  
  <pre><code>/root/software/mongodb-linux-x86_64-2.6.3/bin/mongod&amp;
  </code></pre>
  
  <p><strong>In 2nd phase</strong>, I have various jobs to build some clients.</p>
  
  <p>After 1st phase job, after starting servers and building core part. I see logs- </p>
  
  <pre><code>Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information
  2016-08-26T20:23:00.815+0530 [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
  2016-08-26T20:23:00.833+0530 [signalProcessingThread] now exiting
  2016-08-26T20:23:00.879+0530 [signalProcessingThread] dbexit: 
  2016-08-26T20:23:00.903+0530 [signalProcessingThread] shutdown: going to close listening sockets...
  2016-08-26T20:23:00.903+0530 [signalProcessingThread] closing listening socket: 7
  2016-08-26T20:23:00.903+0530 [signalProcessingThread] closing listening socket: 8
  2016-08-26T20:23:00.903+0530 [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
  Finished: SUCCESS
  </code></pre>
  
  <p>This is stopping all the databases and build is failing for phase2 jobs.</p>
  
  <p>How to tell jenkins not to kill processes after a job?</p>