You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added a fallback mechanism to retrieve commit statuses from the git
provider when the corresponding PipelineRuns are missing from the
cluster due to pruning. This ensures that the retest logic correctly
identifies previously successful templates and avoids re-running them
unnecessarily.
Issues Related (partial): #2580
Jira: https://issues.redhat.com/browse/SRVKP-11112
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
Copy file name to clipboardExpand all lines: docs/content/docs/guides/gitops-commands/_index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ failure is not with your PR but seems to be an infrastructure issue.
25
25
- Previously **failed** PipelineRuns exist for the same commit, OR
26
26
- No PipelineRun has run for the same commit yet
27
27
28
-
If a successful PipelineRun already exists for the same commit, `/retest`**skips** it to avoid unnecessary duplication.
28
+
If a successful PipelineRun already exists for the same commit, `/retest`**skips** it to avoid unnecessary duplication. When PipelineRuns have been pruned from the cluster (for example, by a retention policy), Pipelines-as-Code falls back to querying the Git provider's commit status API to determine which pipelines previously succeeded, ensuring only failed pipelines are re-run even when the original PipelineRun objects no longer exist.
29
29
30
30
**When to use it:** To force a rerun regardless of previous status, use:
0 commit comments