Re: How to keep Unix process alive after job is completed?

Looks very promising. I will give it a try. Thank you, Tim. -jv Am 03.07.2013 17:45, schrieb Tim Ford: John, your issue might be unrelated to Jenkins. See: http://stackoverflow.com/questions/285015/linux-prevent-a-background-process-from-being-stopped-after-closing-ssh-client On Wednesday

Re: How to keep Unix process alive after job is completed?

Could you just have the server process setup as a service and then "start" the service? Richard. On Fri, Apr 26, 2013 at 8:08 PM, hezjing wrote: > Hi > > I have a job which will be run in an Linux slave. > > This job will execute a shell command to start a server process which will > run foreve

Re: How to keep Unix process alive after job is completed?

John, your issue might be unrelated to Jenkins. See: http://stackoverflow.com/questions/285015/linux-prevent-a-background-process-from-being-stopped-after-closing-ssh-client On Wednesday, July 3, 2013 5:42:10 AM UTC-5, John Vacz wrote: > > We have a job executing a shell script (on a slave) t

Re: How to keep Unix process alive after job is completed?

We have a job executing a shell script (on a slave) to restart one dev appserver on a remote server if it does not work properly (dont bother why its not working): # BUILD_ID=dontKillMe ssh user@some.remote.server exec /path/to/appserver/force_restart_script arg1 The "force_restart_scrip

Re: How to keep Unix process alive after job is completed?

Yes, Rakesh On Mon, Apr 29, 2013 at 2:21 PM, hezjing wrote: > Hi Rakesh > > > On Mon, Apr 29, 2013 at 2:16 PM, rakesh menon wrote: > >> Hi hezjing, >> >> I have a same issue . Was adding the above parameter the only thing you >> did or do we do any other additional steps? >> >> Thanks >> >> >>

Re: How to keep Unix process alive after job is completed?

Hi Rakesh On Mon, Apr 29, 2013 at 2:16 PM, rakesh menon wrote: > Hi hezjing, > > I have a same issue . Was adding the above parameter the only thing you > did or do we do any other additional steps? > > Thanks > > > On Mon, Apr 29, 2013 at 7:35 AM, hezjing wrote: > >> Thanks, it works by creat

Re: How to keep Unix process alive after job is completed?

Hi hezjing, I have a same issue . Was adding the above parameter the only thing you did or do we do any other additional steps? Thanks On Mon, Apr 29, 2013 at 7:35 AM, hezjing wrote: > Thanks, it works by create a job parameter BUILD_ID=dontKillMe > > > On Fri, Apr 26, 2013 at 4:16 PM, Riccar

Re: How to keep Unix process alive after job is completed?

Thanks, it works by create a job parameter BUILD_ID=dontKillMe On Fri, Apr 26, 2013 at 4:16 PM, Riccardo Foschia < riccardo.fosc...@meta-level.de> wrote: > Hi, > > Take a look at https://wiki.jenkins-ci.org/**display/JENKINS/** > ProcessTreeKiller

Re: How to keep Unix process alive after job is completed?

Hi, Take a look at https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller section "If your build wants to leave a daemon running behind..." Greetings, Riccardo Am 26.04.2013 10:08, schrieb hezjing: Hi I have a job which will be run in an Linux slave. This job will execute a shell c

How to keep Unix process alive after job is completed?

Hi I have a job which will be run in an Linux slave. This job will execute a shell command to start a server process which will run forever. Unfortunately this process is terminated when the job is finished. When I tested this using PuTTY, the server process is still alive after I logged-in and