Hi everyone!
When I run the executable using the command line, the command kill -2 [pid] helps to terminate the corresponding process.
But when I run the same executable through Jenkins and then type kill -2 [pid] in the command line, it fails to terminate the corresponding process.
I wonder if the process spawned by Jenkins ignores the signal SIGINT?
I don’t think thats something a parent process can do. How are you running the executable, and how are you getting the pid?
Thank you very much for your reply.
How are you running the executable, and how are you getting the pid?
I ran the executable as follows, and then get the child pid spawned by Jenkins from the command line.
I ran the executable as follows, and then get the child pid spawned by Jenkins from the command line.
If I replace command kill -2 [pid] with command kill -15 [pid], the process is successfully terminated, which seems to be the signal SIGTERM works but SIGINT does not.