mirror of
https://github.com/elastic/logstash.git
synced 2025-04-24 14:47:19 -04:00
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
This commit is contained in:
parent
46ba18a1a2
commit
53fe0cd350
1 changed files with 4 additions and 0 deletions
|
@ -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
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue