From 53fe0cd3500b9968ea8c67aa1d67800170aea2df Mon Sep 17 00:00:00 2001 From: Jake Landis Date: Sat, 23 Sep 2017 09:42:59 -0500 Subject: [PATCH] Instruct Jenkins to not abort other Vagrant hosts See: https://stackoverflow.com/questions/19736862/vagrant-aborted-at-end-of-jenkins-job and: https://wiki.jenkins.io/display/JENKINS/ProcessTreeKiller Note - the existing vagrant lifecycle instructs a `destroy` before bootstrapping that will ensure a clean start if last process did not die properly. Fixes #8380 --- ci/acceptance_tests.sh | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ci/acceptance_tests.sh b/ci/acceptance_tests.sh index 8a2d5cccf..188b1c899 100755 --- a/ci/acceptance_tests.sh +++ b/ci/acceptance_tests.sh @@ -15,6 +15,10 @@ SELECTED_TEST_SUITE=$1 [ -f Gemfile ] && rm Gemfile [ -f Gemfile.jruby-2.3.lock ] && rm Gemfile.jruby-2.3.lock +# When running these tests in a Jenkins matrix, in parallel, once one Vagrant job is done, the Jenkins ProcessTreeKiller will kill any other Vagrant processes with the same +# BUILD_ID unless you set this magic flag: https://wiki.jenkins.io/display/JENKINS/ProcessTreeKiller +export BUILD_ID=dontKillMe + if [[ $SELECTED_TEST_SUITE == $"redhat" ]]; then echo "Generating the RPM, make sure you start with a clean environment before generating other packages." rake artifact:rpm