Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[6.8] Jenkins pipeline with parallel cigroups (#45285) #45599

Merged
merged 7 commits into from
Sep 13, 2019

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Sep 13, 2019

Backport of #45285 to 6.8

@spalger spalger force-pushed the backport/6.8/pr-45285 branch from 6639b8e to 06d0174 Compare September 13, 2019 01:02
@spalger spalger force-pushed the backport/6.8/pr-45285 branch from 06d0174 to e1be37c Compare September 13, 2019 01:03
@elastic elastic deleted a comment from elasticmachine Sep 13, 2019
@elastic elastic deleted a comment from elasticmachine Sep 13, 2019
* Pipeline

* WIP some work for parallelization with ciGroups

* Fix xpack kibana install dir, and add some debugging

* Attempt to quick fix a few tests

* Revert "Revert "Revert "[ci] compress jobs for CI stability" (elastic#44584)""

This reverts commit 078ac28.

* Recombine test groups, and try runbld again

* Mostly cleanup, and fix failed_tests reporting to hopefully work for both pipeline and non-pipeline

* Fix typo in shell script

* Remove some debug code

* Add support for changing es transport.port during testing via TEST_ES_TRANSPORT_PORT

* Fix test that uses hard-coded es transport port and add it back in to parallel groups

* Disable checks reporter again for now

* Set env var for TEST_ES_TRANSPORT_PORT in pipeline

* Update Jenkinsfile for shorter testrunner labels

* Fix another hard-coded transport port

* Fix a new test with hard-coded URLs

* Jenkinsfile cleanup and fix one of the groups

* Fix double slash

* Testing vault credentials on jenkins server

* Add a non-existent credential

* Revert "Add a non-existent credential"

This reverts commit 0dc234c.

* Try github-checks-reporter again

* github-checks-reporter should only run for elastic/kibana, forks won't work

* Clean up some debug code

* Changing names around to try to make BlueOcean UI a little better

* Add more stages

* Make some changes to stage structure to mirror a nested example from CloudBees

* Handle TODOs, and some cleanup in Jenkinsfile

* Pass GIT_BRANCH when started without GHPRB, fix branch check

* Fix mailer problem and add code that ensures all tests are in cigroups back in

* Test adding worker/job name to junit report paths

* Remove some duplication from ci_setup scripts

* Fix unit test that uses junit path

* Don't reinstall node every time setup_env is run

* Fix yarn install logic

* Fix another unit test that uses junit output dir

* Download latest ES snapshot after kibana builds

* Make sure junit reports are always processed

* Add two failing tests for testing purposes

* Add support to Jenkinsfile for kibana build e-mails

* Remove some debug code for email sending

* Change JOB env handling in junit paths and move it to a sub-directory

* Revert "Add two failing tests for testing purposes"

This reverts commit 5715203e26922a93483feb0ebb8bb3fdcc3daf8c.

* Fix junit report path in test

* Don't send kibana emails on build abort

* Address PR feedback, formatting and use built-in url formatting library

* Fix path formatting for functional test

* Add email sending back in to Jenkinsfile

* Fix another unit test with path problem

(cherry picked from commit 27d23c4)
@spalger spalger force-pushed the backport/6.8/pr-45285 branch from e1be37c to d8babd2 Compare September 13, 2019 01:04
@spalger
Copy link
Contributor Author

spalger commented Sep 13, 2019

Job completed successfully, but when the test-pipelines label isn't on the issue at the beginning things fall apart a little bit

https://kibana-ci.elastic.co/job/elastic+kibana+pipeline-pull-request/49/

@spalger spalger merged commit 2f67e77 into elastic:6.8 Sep 13, 2019
@spalger spalger deleted the backport/6.8/pr-45285 branch September 13, 2019 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants