-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
Low
-
TestOnly
-
2
-
rhel-pt-c-libs
-
3
-
False
-
False
-
-
None
-
PT C Libraries 2025 S14, PT C Libraries 2025 S15
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
The gating.yaml file defines policies for the osci_compose_gate decision context. We need to determine if an equivalent gating policy is required for the upstream Fedora repository. If so, the existing gating.yaml for RHEL-10 must be ported and adapted for Fedora.
Acceptance Criteria:
Investigate and document whether a gating.yaml is necessary for the Fedora repository's composebuild validation process.- Though I did not find any specific requirement for gating policy in Fedora, other Libraries components have the rules for 'fedora-ci.koji-build.tier0.functional' and it seems like a reasonable step to do. I found an older document that describes setting-up gating for toolchain-qe components. Looking at the current state of the tests in the repo, I removed old tests.yml format and converted existing tests to FMF/TMT and fixed it to work on latest Fedora Rawhide.
If required, port the logic from the existing gating.yaml to a new or updated file in the Fedora repository.
The ported gating.yaml must be updated to reflect Fedora's product versions (e.g., fedora-rawhide) and relevant test case names.
A pull request containing the new or modified gating.yaml is submitted to the appropriate Fedora repository.
If no gating.yaml is needed, document the findings and close this task.