-
Notifications
You must be signed in to change notification settings - Fork 289
OCPQE-30739:Support multi-substring pattern matching for TestGrid #4773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
/retitle "OCPQE-30739:Support multi-substring pattern matching for TestGrid" |
|
@kuiwang02: This pull request references OCPQE-30739 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/retitle OCPQE-30739:Support multi-substring pattern matching for TestGrid |
|
/retest-required |
|
/lgtm |
|
Scheduling required tests: Scheduling tests matching the |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jianzhangbjz, kuiwang02 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@bear-redhat could you please review it? if it is ok, could you please approve it? thanks |
|
/retest-required |
1 similar comment
|
/retest-required |
|
@kuiwang02: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/retest-required |
|
@bear-redhat could you please review it? if it is ok, could you please approve it? thanks |
Refine TestGrid job filtering for operator-framework jobs
Problem
Previously, the
IsSpecialInformingJobOnTestGridfunction used a simple prefix-based matching approach. This meant that all jobs starting with a specific prefix (e.g.,periodic-ci-openshift-operator-framework-operator-controller-orperiodic-ci-openshift-operator-framework-olm-release-) would automatically appear in TestGrid.However, not all jobs in a repository should appear in TestGrid immediately. Some jobs are still stabilizing and should only exist in Sippy as candidate job tier for monitoring purposes. Only stable, production-ready jobs (typically those with
defaultorstablein their names) should be visible in TestGrid and classified as informing jobs.Solution
This PR refines the filtering logic by introducing a flexible pattern-matching system inspired by the
setJobTierfunction insippy/pkg/variantregistry/ocp.go:testGridInformingPrefixesfrom[]stringto[][]stringstrings.HasPrefix)strings.Contains)matchesAllSubstringsfor cleaner code organizationChanges for operator-framework jobs
For operator-framework repositories, this PR adds selective filtering:
Before:
{"periodic-ci-openshift-operator-framework-olm-release-"}, {"periodic-ci-openshift-operator-framework-operator-controller-"}, All jobs with these prefixes appeared in TestGrid. After: {"periodic-ci-openshift-operator-framework-olm-release-", "default"}, {"periodic-ci-openshift-operator-framework-olm-release-", "stable"}, {"periodic-ci-openshift-operator-framework-operator-controller-", "default"}, {"periodic-ci-openshift-operator-framework-operator-controller-", "stable"}, Only jobs containing default or stable in their names appear in TestGrid.Example
For the openshift-operator-framework-operator-controller-release-4.21 periodics:
Jobs without default or stable remain in Sippy as candidate jobs for monitoring but won't clutter TestGrid dashboards. Once these jobs stabilize, teams can rename them to include default or stable, automatically promoting them to TestGrid visibility and informing tier.
Benefits
Testing
Comprehensive unit tests were added to verify the behavior:
Test coverage includes:
Assisted-by: Claude Code