* gather up all the flaky test stuff into a directory
* create Jenkins Pipeline DSL for the report generation and the flaky re-testing
* have the nightly per-branch job consume the results of flaky reporting
Signed-off-by: Mike Drob <mdrob@apache.org>
Conflicts:
dev-support/Dockerfile
dev-support/Jenkinsfile
dev-support/flaky-tests/flaky-dashboard-template.html
dev-support/flaky-tests/report-flakies.py
For branches 1, includes a backport of the current version of report-flakies.py
and supporting files.
* in a post-step, build status can either be "null" or "SUCCESS" to indicate success.
* before we do an scm checkout for stages that post to the comment, set a default "we failed ¯\_(ツ)_/¯" comment.
Signed-off-by: Michael Stack <stack@apache.org>
Signed-off-by: Mike Drob <mdrob@apache.org>
* Ensure Jenkins steps that invoke bash inline set -e
* machine stats script should check that passed directory will work
Signed-off-by: Michael Stack <stack@apache.org>
* do a scm checkout on the stages that need access to source.
* ensure our install job runs on the ubuntu label
* copy jira comments to main workspace
* simplify the jira comment
Signed-off-by: Michael Stack <stack@apache.org>
- rely on parallel pipeline to ensure all stages always run
- define non-CPS jira commenting function
- comment on jiras in the changeset with summary and links
Signed-off-by: Mike Drob <mdrob@apache.org>
Conflicts:
dev-support/Jenkinsfile
Jenkins fails the whole build immediately if any stage fails. Hadoop2 tests run before Hadoop3 tests.
So Hadoop3 tests will run only if hadoop2 tests pass.
- Stop presuming job will be configured with checkout into a 'component' dir
- Disable autocheckout
- Specify checkout within 'component' dir
- leave the workspace around on pipeline failure so we can browse it.
* Jenkinsfile that works for all current branches.
* adds dev-support script for setting parameters for our yetus nightly invocation
* quiets the "zip test results" step
Signed-off-by: tedyu <yuzhihong@gmail.com>