cicd ignore reused object total timing

2026-07-03 11:44:27 +00:00
parent 76c2a58996
commit 75f205a539
2 changed files with 4 additions and 0 deletions
@@ -68,6 +68,8 @@ Stage timing must be queryable through normal CLI output, not only raw JSON. `st

 Do not backfill, infer, or migrate old branch-follower state when historical timing, stage timing, or other observability fields are missing or known to be unreliable. Compatibility starts with future state written by the current controller; old missing data must render as `-`/unknown in CLI output instead of being recovered from unrelated native objects.

+If a deterministic Kubernetes Job or PipelineRun is reused and there is no already-stored `timings.startedAt`, the reused object's current wait/check duration is only a stage observation; it must not be promoted to `timings.totalSeconds`.
+
 State machine phases are `Observed`, `Noop`, `PendingTrigger`, `Triggering`, `ClosingOut`, `Succeeded`, `Failed`, `Superseded`, `Blocked`, and `Skipped`.

 Status and decision inputs are Kubernetes-native: