From a7e2e137f27b8f040888df4d67469c73f4d2fe8c Mon Sep 17 00:00:00 2001 From: Jan Pazdziora Date: Jun 10 2019 08:53:29 +0000 Subject: Gate on package test results. In https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/5QVYP53EO5O43UCRQSTNUP2M3YSE24MM/ Adam suggests that `dist.depcheck` hasn't been used for a while I've checked that `org.centos.prod.ci.pipeline.allpackages-build.package.test.functional.complete` will cause gating to stop errata when tests for the package fail in Fedora CI. --- diff --git a/modules/ROOT/pages/gating.adoc b/modules/ROOT/pages/gating.adoc index a3ffa3e..f6fc0d6 100644 --- a/modules/ROOT/pages/gating.adoc +++ b/modules/ROOT/pages/gating.adoc @@ -12,11 +12,19 @@ If you want to turn the gating on for your component create a new file `gating.y - fedora-* decision_context: bodhi_update_push_testing rules: - - !PassingTestCaseRule {test_case_name: dist.depcheck} + - !PassingTestCaseRule {test_case_name: org.centos.prod.ci.pipeline.allpackages-build.package.test.functional.complete} + --- !Policy + product_versions: + - fedora-* + decision_context: bodhi_update_push_stable + rules: + - !PassingTestCaseRule {test_case_name: org.centos.prod.ci.pipeline.allpackages-build.package.test.functional.complete} This will enable gating for all Fedora releases based on the result of the CI xref:pipeline.adoc[Pipeline]. The `decision_context` is to be https://pagure.io/greenwave/issue/282[clarified]. -Rules define test cases that should be considered for the gating decision, in this case `dist.depcheck`. +Rules define test cases that should be considered for the gating decision, in this case +`org.centos.prod.ci.pipeline.allpackages-build.package.test.functional.complete` which are tests that were run +in the CI based on the configuration in `tests/tests.yml` in package's dist-git. Other tests which can be enabled for gating: * https://fedoraproject.org/wiki/Taskotron/Tasks/dist.rpmdeplint[dist.rpmdeplint] - to make sure the update's dependencies are available