For my current performance test project, I’m using Jenkins to fire off jmeter. The jmeter tests themselves are spawned on multiple load test clients and so I need to start the jmeter-server on each of these clients.
I ran into problems when doing this via the Jenkins ‘Execute Shell’ module:
nohup ./jmeter-server &
As soon as Jenkins shell module completed, the Jmeter server was no longer alive. A ‘ps -ef | grep jmeter’ showed no results as the process was killed.
This blog post really helped me – in fact, it probably saved me my job! Apparently, the Jenkins shell kills the shell process as well as the shell’s children processes – no bueno… To fix this, simply include the following snipped in your Jenkins shell module
BUILD_ID=dontKillMe
Given blog is not available.
Can you please update the link if possible.
I pulled up a copy on the way back machine (really useful if a web page is no longer available)!
https://web.archive.org/web/20130102130412/http://reverb.findawayworld.com/development/using-jenkins-to-run-a-web-server-without-killing-it/
Thank you very much Mr Benjamin.
Its very helpful for me.