diff --git a/.gitlab/merge_request_templates/Default.md b/.gitlab/merge_request_templates/Default.md index b0ac0602108e3f94870b5f803d31e69f01fc8150_LmdpdGxhYi9tZXJnZV9yZXF1ZXN0X3RlbXBsYXRlcy9EZWZhdWx0Lm1k..ceee06cbc37b2f3b82c9bf315698f68e4ededfd0_LmdpdGxhYi9tZXJnZV9yZXF1ZXN0X3RlbXBsYXRlcy9EZWZhdWx0Lm1k 100644 --- a/.gitlab/merge_request_templates/Default.md +++ b/.gitlab/merge_request_templates/Default.md @@ -28,6 +28,7 @@ If you don't have access to this, the reviewer should trigger these jobs for you during the review process. - [ ] The manual `Trigger:ee-package` jobs have a green pipeline running against latest commit. + - To debug QA failures, refer to the [Investigate QA failures](https://about.gitlab.com/handbook/engineering/quality/quality-engineering/enablement-saas-platforms-qe-team/distribution/#investigate-qa-failures) section. - [ ] If `config/software` or `config/patches` directories are changed, make sure the `build-package-on-all-os` job within the `Trigger:ee-package` downstream pipeline succeeded. - [ ] If you are changing anything SSL related, then the `Trigger:package:fips` manual job within the `Trigger:ee-package` downstream pipeline must succeed. - [ ] If CI configuration is changed, the branch must be pushed to [`dev.gitlab.org`](https://dev.gitlab.org/gitlab/omnibus-gitlab) to confirm regular branch builds aren't broken. diff --git a/doc/development/allure-test-report.md b/doc/development/allure-test-report.md index b0ac0602108e3f94870b5f803d31e69f01fc8150_ZG9jL2RldmVsb3BtZW50L2FsbHVyZS10ZXN0LXJlcG9ydC5tZA==..ceee06cbc37b2f3b82c9bf315698f68e4ededfd0_ZG9jL2RldmVsb3BtZW50L2FsbHVyZS10ZXN0LXJlcG9ydC5tZA== 100644 --- a/doc/development/allure-test-report.md +++ b/doc/development/allure-test-report.md @@ -1,5 +1,7 @@ # Test Report Generation in Omnibus-GitLab +[[_TOC_]] + The following three pipelines are created while generating the allure-report - Omnibus pipeline @@ -87,3 +89,8 @@ end end ``` + +## Demo for Allure report & QA pipelines + +An in-depth video walkthrough of the pipeline and how to use Allure report +is available [on YouTube](https://youtu.be/_0dM6KLdCpw). diff --git a/doc/development/pipelines.md b/doc/development/pipelines.md index b0ac0602108e3f94870b5f803d31e69f01fc8150_ZG9jL2RldmVsb3BtZW50L3BpcGVsaW5lcy5tZA==..ceee06cbc37b2f3b82c9bf315698f68e4ededfd0_ZG9jL2RldmVsb3BtZW50L3BpcGVsaW5lcy5tZA== 100644 --- a/doc/development/pipelines.md +++ b/doc/development/pipelines.md @@ -250,6 +250,9 @@ developers to get a package or Docker image for testing, or to run a full QA suite against their MR's changes. +To debug QA failures, refer to the [Investigate QA failures](https://about.gitlab.com/handbook/engineering/quality/quality-engineering/enablement-saas-platforms-qe-team/distribution/#investigate-qa-failures) +section. This job also generates Allure report, see more information and the demo at [Test Report Generation in Omnibus-GitLab](allure-test-report.md). + This job is run only on [Development repository](https://gitlab.com/gitlab-org/omnibus-gitlab) and [Security mirror](https://gitlab.com/gitlab-org/security/omnibus-gitlab) on branch pipelines.