We have a pipeline which deploys our main product (a java app inside an
application container)
I have used the env variable *JENKINS_NODE_COOKIE* to instruct Jenkins to
not kill the process.
For example:
withEnv(['JENKINS_NODE_COOKIE=dontkill']) {
// start your process here
sh 'java -jar ...'
}
On Wed, Jun 12, 2019 at 2:31 PM Renato Goncalves <rengo...@broadsoft.com>
wrote:
> Hello guys,
>
> I am performing a few tests regarding NSO maintenance automation and the
> behaviour of NSO is not what I was expecting. During the pipeline, I stop
> the NSO daemon (ncs --stop) and restart it with (ncs
> --with-package-reload-force). I created 2 pipelines: the first is a dry-run
> and the second is a commit. In both cases, at the end of the pipeline,
> Jenkins is killing the NSO daemon. The python script to perform the
> injection of new configuration (push_config.py) doesn't use a daemon, it is
> a simple python script that sends commands using python's request library.
> I think I can trap the SIGTERM SIGKILL SIGQUIT in the "push_config.py"
> script so it would not let Jenkins kill the daemon. It would likely
> preclude the graceful stop with the OS too though. This is the current
> output --> https://pastebin.com/LEMCuNMP Do you guys have any idea
> regarding this behaviour, did you have this problem in the past?
>
>
> This email is intended solely for the person or entity to which it is
> addressed and may contain confidential and/or privileged information. If
> you are not the intended recipient and have received this email in error,
> please notify BroadSoft, Inc. immediately by replying to this message, and
> destroy all copies of this message, along with any attachment, prior to
> reading, distributing or copying it.
>
> Ce message confidentiel et les éventuelles pièces jointes sont à l’usage
> exclusif de son ou de sa destinataire. Il est interdit, pour toute autre
> personne, de le distribuer, d’en dévoiler le contenu ou de le reproduire.
> Si vous avez reçu cette communication par erreur, veuillez en informer
> immédiatement l’expéditeur par courrier électronique et détruire l’original
> de ce message ainsi que toute copie.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/72cdf2bd-f53f-4f4c-8870-c42f6095dfcf%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/72cdf2bd-f53f-4f4c-8870-c42f6095dfcf%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CADCvpUdHC5CTgBJ%2BQ8s%2B3GyW70CHvKHp%2B-maOmVTOSNTG0oiSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
