[WIP] - Add code to execute pre-submits by tag

[kasturinarra]

This PR introduces a command in github like /pj-rehearse {tag-name} where {tag-name} could be something like TNF. That command would look up the relevant available TNF tests and try to schedule rehearsals of the ones that match.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kasturinarra
Once this PR has been reviewed and has the lgtm label, please assign prucek for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kasturinarra]

/retest-required

[kasturinarra]

/test breaking-changes

[openshift-ci]

@kasturinarra: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/breaking-changes	991712b	link	false	/test breaking-changes

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.

[droslean]

@kasturinarra Can you elaborate more? On the first look I don't think that this feature makes any sense for the rehearse plugin. This tool is not supposed to rehearse jobs provided by the user. Let's try to figure out what is needed first and how we can implement it.

[kasturinarra]

@kasturinarra Can you elaborate more? On the first look I don't think that this feature makes any sense for the rehearse plugin. This tool is not supposed to rehearse jobs provided by the user. Let's try to figure out what is needed first and how we can implement it.

@droslean here is what i am trying to achieve using the PR here, Improve this by introducing a command in github like /pj-rehearse {tag-name} where {tag-name} could be something like TNF. That command would look up the relevant available TNF tests and try to schedule rehearsals of the ones that match.

[kasturinarra]

@kasturinarra Can you elaborate more? On the first look I don't think that this feature makes any sense for the rehearse plugin. This tool is not supposed to rehearse jobs provided by the user. Let's try to figure out what is needed first and how we can implement it.

@droslean here is what i am trying to achieve using the PR here, Improve this by introducing a command in github like /pj-rehearse {tag-name} where {tag-name} could be something like TNF. That command would look up the relevant available TNF tests and try to schedule rehearsals of the ones that match.

@droslean I think there might be a misunderstanding about what this feature does. This is NOT about allowing users to rehearse arbitrary jobs.

The tag-based selection works WITHIN the existing rehearsal system:

1. Existing flow: PR changes → Rehearsal intelligence determines affected jobs → User runs /pj-rehearse {specific-job-names}
2. Enhanced flow: PR changes → Rehearsal intelligence determines affected jobs → User runs /pj-rehearse-by-tag {tag} → System filters affected jobs by tag

The key point is that we're only adding tag-based filtering to jobs that the rehearsal system has already determined are affected by the PR changes. We're not bypassing any existing safety mechanisms.

Problem we're solving: With 81k+ presubmit jobs, developers can't discover which tests are relevant to their changes. Tags like tnf, telco, storage help group related tests for better discoverability.

Example scenario:

• Developer makes changes to telco-related code
• Rehearsal system identifies 50 affected jobs
• Instead of needing to know specific job names, developer can run /pj-rehearse-by-tag telco
• System runs only the telco-tagged jobs from those 50 affected jobs

This maintains all existing safety while improving usability. Does this clarify the intent?

[deepsm007]

math.MaxInt concerns us

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale