When you cancel a Jenkins job
Unfinished draft; do not use until this notice is removed.
We were seeing some unexpected behavior in the processes that Jenkins launches when the Jenkins user clicks "cancel" on their job. Unexpected behaviors like:
- apparently stale lockfiles and pidfiles
- overlapping processes
- jobs apparently ending without performing cleanup tasks
- jobs continuing to run after being reported "aborted"