The tramp is interrupted at the end of Jenkins work

I had this problem for a while. Stray boxes break off at the end of Jenkins' work. I limited only the script to work with

vagrant up sleep 60 

Within 60 seconds, stray boxes are launched, and the second - the completion of the work of stray boxes.

+6
source share
2 answers

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.

+7
source

You may be using an older version of the Jenkins plugin, but now it contains a β€œDo not Kill Me” checkbox. You must check this to save vm.

' jenkins config '

-1
source

Source: https://habr.com/ru/post/957225/


All Articles