Story (Required)

As a developer trying to trigger OpenShift CI pipelines for PRs from untrusted users, I want the /retest command to only restart necessary pipelines, so that unnecessary pipeline runs are avoided.

Background (Required)

The /retestt command is used to start OpenShift CI pipelines (Prow) for PRs from untrusted users. Currently, when the command is used, it restarts all pipelines, even if they were already green. This behavior is inefficient and may be related to [openshift-pipelines/pipelines-as-code#1811|https://github.com/openshift-pipelines/pipelines-as-code/issues/1811]. The differing behaviors between OpenShift CI and Prow commands add to the confusion.

Out of scope

• Changing the behavior of Prow commands.
• Modifying the pipeline logic beyond the /retest command.

Approach (Required)

• Investigate the logic behind the /retest command in Konflux.
• Ensure the command only triggers pipelines that are necessary (e.g., failed or not yet run).
• Align the behavior with OpenShift CI/Prow expectations if possible.

Dependencies

• [openshift-pipelines/pipelines-as-code#1811|https://github.com/openshift-pipelines/pipelines-as-code/issues/1811]

Acceptance Criteria (Mandatory)

• /retest does not restart pipelines that are already green.
• The command only triggers pipelines that are necessary (e.g., failed or not yet run).
• No regression in pipeline behavior for trusted users.

INVEST Checklist

• Dependencies identified: Yes
• Blockers noted: None
• Design is implementable: Yes
• Acceptance criteria agreed upon: Yes
• Story estimated: Pending

Done Checklist

• Code is completed, reviewed, documented, and checked in.
• Unit and integration test automation delivered and running cleanly.
• Continuous Delivery pipeline(s) can proceed with new code.
• Customer-facing documentation is updated and published.
• Acceptance criteria are met.