| |
@@ -29,15 +29,19 @@
|
| |
|
| |
TIP: In order to enable both gates, simply concatenate both examples above.
|
| |
|
| |
+ TIP: To add another test just extend the `rules` list with additional `!PassingTestCaseRule`.
|
| |
+
|
| |
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
|
| |
`fedora-ci.koji-build.tier0.functional` 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
|
| |
- * https://fedoraproject.org/wiki/Taskotron/Tasks/dist.abicheck[dist.abicheck] - to make sure the update's ABI remains stable in stable Fedora releases
|
| |
+ * https://github.com/fedora-ci/rpmdeplint-pipeline[fedora-ci.koji-build.rpmdeplint.functional] - to make sure the update's dependencies are available
|
| |
+ * https://github.com/fedora-ci/rpminspect-pipeline[fedora-ci.koji-build.rpminspect.static-analysis] - to check package sanity including ABI stability
|
| |
+ * https://github.com/fedora-ci/installability-pipeline[fedora-ci.koji-build.installability.functional] - to make sure package installation / update works well
|
| |
|
| |
See Greenwave's https://docs.pagure.org/greenwave/package-specific-policies.html[Package-specific policies] for more technical details about setting the policy.
|
| |
|
| |
mvadkert
commented 3 years ago
While reviewing this page I found a few things to update:
Signed-off-by: Miroslav Vadkerti mvadkert@redhat.com