mirrors/pikasTech-unidesk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

cicd track follower timing start and finish

Browse Source
This commit is contained in:
Codex
2026-07-03 11:31:48 +00:00
parent 63de02e3a2
commit 8557ab3553
3 changed files with 55 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/skills/unidesk-cicd/references/branch-follower.md
+1 -1
View File
@@ -64,7 +64,7 @@ Default `status` output must show follower id, phase, adapter, source branch + o
Stage timing must be queryable through normal CLI output, not only raw JSON. `status` and `run-once` print a bounded `STAGE TIMINGS` table with `total`, `status-read`, git-mirror, Kubernetes Job, PipelineRun, TaskRun, Argo, runtime and closeout rows when available. `followers[].timings` remains available in `--raw`/JSON for machine consumers.
`timings.totalSeconds` is the authoritative end-to-end wall-clock measurement for a triggered run: measure from the adapter/controller starting that source-change operation until success, failure, or closeout timeout. Do not compute total by summing stage rows, because stage rows can overlap, omit external waiting, or be reported by different native objects.
`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.
State machine phases are `Observed`, `Noop`, `PendingTrigger`, `Triggering`, `ClosingOut`, `Succeeded`, `Failed`, `Superseded`, `Blocked`, and `Skipped`.