kibana/test/scripts/jenkins_unit.sh

#!/usr/bin/env bash

set -e
source "$(dirname $0)/_jenkins_setup.sh"

xvfb-run "$(npm bin)/grunt" jenkins:unit;
[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`
[ci] source the setup script instead of executing it 2016-07-05 21:46:53 +02:00			`source "$(dirname $0)/_jenkins_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] source the setup script instead of executing it 2016-07-05 21:46:53 +02:00			`xvfb-run "$(npm bin)/grunt" jenkins:unit;`