This behavior is caused by the Jenkins process tree . I got it to work by running Jenkins as follows:
java -Dhudson.util.ProcessTree.disable=true -jar jenkins-1.537.war
Another (less global) approach is to start a tramp as follows:
BUILD_ID=dontKillMe vagrant up
It makes sense in retrospect. The processes started by the Jenkins task must be cleared at the end. Of course, it will be "gotcha", you are trying to use Jenkins to run long processes.
+1 for this question.
source share