Commit graph

9 commits

Author SHA1 Message Date
jasper
d2a06c4bbf build: always run build task in jenkins (#10694)
Backports PR #10689

**Commit 1:**
build: always run build task in jenkins

We always run the build task now in jenkins jobs rather than only in the
core builds. This ensures that the build task runs in PR builds even
though the build artifacts are not used for anything.

Ideally all the selenium tests would run against this build rather than
it just being something that gets ran and forgotten about, but this is a
first step.

* Original sha: 9517d8ded4
* Authored by Court Ewing <court@epixa.com> on 2017-03-03T16:11:20Z
2017-03-03 13:22:21 -05:00
spalger
8adaecb9be [ci] source the setup script instead of executing it 2016-07-05 12:46:53 -07:00
spalger
e98c3d4c42 [ci] tweak ci scripts to debug 2016-07-05 11:08:22 -07:00
spalger
ee29dc6d02 [ci] make jenkins selenium script executable 2016-07-01 12:32:03 -07:00
spalger
b7c8db694a [ci] run the unit tests with xvfb-run 2016-07-01 12:22:39 -07:00
spalger
55d95790ea [ci] call xvfb-run before selenium tasks 2016-07-01 11:35:56 -07:00
spalger
7df6040536 [ci] split unit and selenium tasks into separate jenkins scripts 2016-07-01 11:31:02 -07:00
spalger
995c408410 [ci] add script for snapshot build job 2016-06-30 15:41:47 -07:00
spalger
cb0659f98d [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 12:50:56 -07:00