-
Notifications
You must be signed in to change notification settings - Fork 0
Jenkins CI
As of July 6th Kibana migrated PR and snapshot CI jobs to https://kibana-ci.elastic.co. This change introduces some changes, and seemed like a good time to write some docs.
CI jobs are triggered when changes are pushed to a pull request or a version branch (master, 5.x, etc.). On each change a "MultiPhase Projects" will be kicked off for the specific commit that was submitted. These meta jobs are currently just made up of two parts, the "intake" phase and the "selenium" phase. This is likely to change as we mature our CI strategy.
- test changes pushed to master: elastic / kibana # master
- build snapshots of each valid push to master: elastic / kibana # master - upload snapshot
- test pr changes: elastic / kibana # master - pull requests
When a job fails you can figure out what happened by looking at the console output produced. To find the console output:
-
Open the project for the failed job
-
Open the page for the failed build by finding it in the Build History column on the left of the project index
- Click the "Console Output" link for the phase that failed
- Search the console output (there is probably a lot of it) to figure out what went wrong.
Can't find the failure in the intern output? For Intern based tests, failures are logged inline amongst a ton of other output so they can be a bit hard to find. Click the "Full Log" link at the top of the log output and search for "> FAIL:" for find them.
If your PR was not properly validated, but you are confident that it was because of some strange hiccup in the environment (selenium race condition, git hiccup, etc.) then you can try rerunning the tests with the comment "jenkins, test it".