cicd recover follower total timing from native state

2026-07-03 11:35:12 +00:00
parent 8557ab3553
commit c9824a5847
2 changed files with 22 additions and 2 deletions
@@ -66,6 +66,8 @@ Stage timing must be queryable through normal CLI output, not only raw JSON. `st

 `timings.totalSeconds` is the authoritative end-to-end wall-clock measurement for a triggered run: measure from `timings.startedAt` until `timings.finishedAt`, or until query time while closeout is still running. Do not compute total by summing stage rows, because stage rows can overlap, omit external waiting, or be reported by different native objects.

+If a controller loop resumes an already-triggered source change and the stored state predates `startedAt`, it may recover the total timer from the native PipelineRun start time and then persist that recovered start point.
+
 State machine phases are `Observed`, `Noop`, `PendingTrigger`, `Triggering`, `ClosingOut`, `Succeeded`, `Failed`, `Superseded`, `Blocked`, and `Skipped`.

 Status and decision inputs are Kubernetes-native: