nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What happens when bamboo stops a build?

Matthew Grasse

On linux one step of my build runs a bash script which in turn spawns a number of other processes. When the build is stopped in bamboo, I see that some of the processes continue to run on the build agent.

I assume that I need to clean up my processes when the build is being stopped, but I don't know exactly what happens when the stop occurs. How does bamboo implement the task stopping? Does it send the child process a signal? If so, which signal is it?

Accepted answers

Brent Villalobo1

I don't know the exact mechanisms Bamboo uses when you stop a build, but we had to workaround the orphan process problem by creating an "orphan killer" daemon on the machine that periodically looked for Bamboo-owned processes with a parent PID of 1.

There is a "Hung Build Killer" plugin for Bamboo. I've never used it, but you may be able to peak at the source to get an idea of how it handles the orphaned processes.

All comments

Brent Villalobo1

There is a "Hung Build Killer" plugin for Bamboo. I've never used it, but you may be able to peak at the source to get an idea of how it handles the orphaned processes.

Matthew Grasse

Thanks, Brent. This isn't quite what I'm looking for - I'd like to be able to handle the stopping case in my scripts, but this is the most helpful information I've found.

neostorm

After writing a script to trap the signal the following takes place when you stop the build in the middle of it running a script

"Broke n Pipe"
$SIG{PIPE}

David Rothlisberger

Bamboo sends SIGTERM to the script.

Tested with Bamboo 6.4.1 on Linux, by creating the following script, running a build, then stopping it:

#!/bin/sh
trap 'echo sigterm handler > /tmp/bamboo.log' TERM
sleep 100 &
wait

Note that your SIGTERM handler will actually have to kill your own child processes, which isn't always trivial on Linux.