Starting a forever process in a Jenkins build step?

Question

I'm running a shell command at the end of a Jenkins deployment to restart a forever script:

npm install && forever stop app.js && forever start -a -l /var/log/forever.log app.js

When I run that as a user jenkins everything works fine and the console output from the build history also tells me that the forever script is running. However, the process stops right after the deployment is finished and the forever process is stopped.

What causes this behavior and how can I fix it?

score 29 · Accepted Answer · answered Apr 25 '13 at 18:45

29

Jenkins kills all process spawn by the job.

This can be disabled by setting the BUILD_ID environment variable to something else:

export BUILD_ID=dontKillMe

see https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller for details

answered Apr 25 '13 at 18:45

rcomblen

476
4
5

1

Is this a 'clean' way to do or something else recommended? – Patrick Apr 26 '13 at 10:17
As far as I know, it's the only way to disable the ProcessTreeKiller – rcomblen Apr 26 '13 at 13:00
rcomblen is correct, check out https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller – Jan Molak Jan 02 '14 at 18:13
Before this I was getting. [ssh-agent] Stopped. Killed by signal 15. Killed by signal 15. After this I got [ssh-agent] Stopped. But it is still being killed :( – Amit Kumar Gupta Mar 15 '16 at 17:09
The link is dead now. The only reference I found so far is https://www.jenkins.io/doc/developer/extensions/jenkins-core/#processkiller. – Gerold Broser Sep 09 '21 at 21:28

score 3 · Answer 2 · answered Feb 09 '18 at 19:56

3

In the new Pipeline jobs, setting BUILD_ID no longer works. Instead, you need to set JENKINS_NODE_COOKIE to prevent Jenkins from killing your process when the job finishes.

sh 'export JENKINS_NODE_COOKIE=dontKillMe'
sh 'myProcess'

Or, more selectively:

sh 'JENKINS_NODE_COOKIE=dontKillMe myProcess'

See the wiki on ProcessTreeKiller and this comment in the Jenkins Jira.

answered Feb 09 '18 at 19:56

jpyams

435
4
7

Isn't each `sh` step its own shell? I don't think the export in your first shell is going to exist in the second shell. – Michael Mrozek May 24 '22 at 19:50

score 2 · Answer 3 · answered Jan 23 '17 at 11:43

The question is quite old, but there is a better solution in this case I think.

Use Post-Build Script Plug-In

The plugin itself is not updated since the beginning of 2016, but it does the job and you do not have to fiddle with environment variables. Seems a bit neater to me.

score 0 · Answer 4 · answered Dec 20 '19 at 14:28

0

Try with:

(
  set -e
  export BUILD_ID=dontKillMe
  export JENKINS_NODE_COOKIE=dontKillMe
  npm install
  forever stop app.js
  forever start -a -l /var/log/forever.log app.js &
) &

answered Dec 20 '19 at 14:28

Eduardo Cuomo

192
1
5

Starting a forever process in a Jenkins build step?

4 Answers4