Learn more about these different git repos.
Other Git URLs
The policy docs give a simple example for how to opt in to gating for pushing to stable:
--- !Policy id: taskotron_release_critical_tasks decision_context: bodhi_update_push_stable subject_type: bodhi_update product_versions: - fedora-26 - fedora-27 rules: - !PassingTestCaseRule {test_case_name: dist.rpmdeplint} - !PassingTestCaseRule {test_case_name: dist.upgradepath} blacklist: - qt - mariadb
It would be good to document how users could form separate testing and stable policies. I attempted to do this in Bodhi but was just guessing as to the syntax.
We think we can create a good user experience for how to do this with the proposed solution to #282
I think this is a duplicate of #282.
@bowlofeggs We went through couple of changes in documentation: https://docs.pagure.org/greenwave/package-specific-policies.html#
Is it clear now? Any specifics we need to add?
@lholecek it should probably give an example of a single policy file that has one set of tests to gate for testing and another set of tests to gate for stable.
This is currently documented in Fedora documentation itself which is a better place for it anyways: https://docs.fedoraproject.org/en-US/ci/gating/
Metadata Update from @lucarval: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.