kibana/test/scripts/jenkins_unit.sh

#!/usr/bin/env bash

set -e
source "$(dirname $0)/../../src/dev/ci_setup/setup.sh"
source "$(dirname $0)/../../src/dev/ci_setup/git_setup.sh"
source "$(dirname $0)/../../src/dev/ci_setup/java_setup.sh"

export TEST_ES_FROM=${TEST_ES_FROM:-source}
xvfb-run "$(FORCE_COLOR=0 yarn bin)/grunt" jenkins:unit --from=source;
[ci] move ci setup tasks into source control Until now, the ci setup tasks were stored in the Jenkins job configuration. This moves the setup into source control so that jenkins can be told to execute `./test/scripts/jenkins_{JOB_TYPE}.sh` no matter what branch of kibana it is dealing with. 2016-06-30 21:50:56 +02:00			`#!/usr/bin/env bash`

			`set -e`
[dev/ci_setup] generalize jenkins_setup script for other CI environments (#15178) * [dev/ci_setup] generalize jenkins_setup script for other CI environments * [dev/ci_setup] accept more general `CACHE_DIR` env arg * [dev/ci_setup] node.js install might not be invalid 2017-11-30 18:26:03 +01:00			`source "$(dirname $0)/../../src/dev/ci_setup/setup.sh"`
Migrate x-pack-kibana source to kibana 2018-04-20 21:13:37 +02:00			`source "$(dirname $0)/../../src/dev/ci_setup/git_setup.sh"`
			`source "$(dirname $0)/../../src/dev/ci_setup/java_setup.sh"`
[ci] move ci setup tasks into source control Until now, the ci setup tasks were stored in the Jenkins job configuration. This moves the setup into source control so that jenkins can be told to execute `./test/scripts/jenkins_{JOB_TYPE}.sh` no matter what branch of kibana it is dealing with. 2016-06-30 21:50:56 +02:00
[ci] Run ES snapshot when possible (#22663) For instances where we would otherwise be running from source in a tracked elastic/elasticsearch branch, let's use a snapshot instead. This will eliminate some gradle issues we are experiencing in master. 2018-09-07 01:31:47 +02:00			`export TEST_ES_FROM=${TEST_ES_FROM:-source}`
[mocha] remove grunt-simple-mocha (#19079) * [mocha] run tests with mocha script, remove grunt-simple-mocha * [ci] force colored output * [ci] disable color when reading the yarn bin * [dev/build/exec] support tooling log having its own chalk * [dev/mocha] avoid changing the cwd of the process * [dev/mocha] only match files, speed up negative matches * [cli/serve/test] strip ansi control characters from logs * [ci] disable color in all `yarn bin` invocations * [dev/mocha] cleanup old runInBand check * [dev/mocha] enable gloabl leak checks 2018-05-16 19:43:55 +02:00			`xvfb-run "$(FORCE_COLOR=0 yarn bin)/grunt" jenkins:unit --from=source;`