Jenkins makes use of a feature called the ProcessTreeKiller to kill processes when aborting a build (e.g., timeout, manual abort, etc.). The ProcessTreeKiller checks the environment of all processes to see if they contain the BUILD_ID of the current build, and if they do, it kills them.
The ProcessTreeKiller doesn't support FreeBSD though, as it depends on being able to read the environment from procfs.
In theory, it should be able to modify the ProcessTree implementation in Jenkins to support this, so that it works as expected. Doing so might be quite some work (especially when trying to upstream a patch).
So if fixing the problem isn't possible, it would be good if the port would warn about it (and recommending a workaround).
I'm currently using the script below, called from within a shell build step, to emulate expected ProcessTreeKiller behavior:
# 2021 Michael Gmelin <grembo@FreeBSD.org>
# When aborting a build, Jenkins kills all processes containing
# the correct BUILD_ID in their environment using the
# As the ProcessTreeKiller is not supported on FreeBSD,
# aborting a build can leave processes behind.
# This script mitigates this by waiting for the
# script it was executed by to end and then
# emulating ProcessTreeKiller behavior (check
# all processes if they're containing BUILD_ID=<build_id>
# in their environment.
# Example invocation from build script:
# (env -u BUILD_ID build_cleanup.sh "$$" "$BUILD_ID")&
for p in $(ps -xopid | grep -v PID); do
if [ "$p" -ne "$$" ]; then
procstat -e $p 2>/dev/null | tr " " "\n" | grep -q "BUILD_ID=$2"
if [ $? -eq 0 ]; then
(env -u BUILD_ID build_cleanup.sh "$$" "$BUILD_ID")&
Is this fixed here?