|
|
| (2 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| Gating of packages based on test results is currently enabled on demand. If you want to turn the gating on for your component create a new file `gating.yaml` in the root of the package dist git directory with the following content:
| | Moved to: https://docs.fedoraproject.org/en-US/ci/gating/ |
| | |
| --- !Policy
| |
| product_versions:
| |
| - fedora-*
| |
| decision_context: bodhi_update_push_testing
| |
| rules:
| |
| - !PassingTestCaseRule {test_case_name: dist.depcheck}
| |
| | |
| This will enable gating for all Fedora releases based on the result of the CI [[CI/Pipeline|Pipeline]]. The `decision_context` is to be [https://pagure.io/greenwave/issue/282 clarified].
| |
| | |
| == Waiving ==
| |
| | |
| If the failed test result is irrelevant you can waive it using the bodhi web interface or directly from the command line.
| |
| | |
| # List blocking test results
| |
| bodhi update waive <id> --show
| |
| | |
| # Specify which tests to waive via:
| |
| bodhi update waive <id> --test="dist.rpmlint" --test="atomic-ci" "Comment explaining the waiver"
| |
| | |
| # Waive all tests:
| |
| bodhi update waive <id> --test=all "Comment explaining the waiver"
| |
| | |
| While web UI only allow to waive all tests command line provides a way to select tests which should be waived.
| |
| | |
| == Links ==
| |
| | |
| * Greenwave's [https://docs.pagure.org/greenwave/package-specific-policies.html Package-specific policies]
| |
| * [https://pagure.io/fesco/issue/1966 Allow turning on opt-in gating] issue
| |
| * [https://github.com/fedora-infra/bodhi/pull/2468 Implement the possibility to waive missing requirements via bodhi-cli]
| |
Latest revision as of 15:49, 18 March 2019
