Show full audited run graphs and scope searchable run history
This commit is contained in:
+15
-5
@@ -10,7 +10,13 @@ separately. Set `PIPELINES_URL` or pass `--url` to select another server.
|
||||
|
||||
## Dashboard and status
|
||||
|
||||
Home's `r` opens **all** recent runs (latest 50), not only failures. Wide terminals
|
||||
Home's `r` opens **all** runs, not only failures or the newest 50. Inside a pipeline,
|
||||
`r` and `:runs` show only that pipeline's runs across its versions. In any run list,
|
||||
press `/` for fuzzy search, type to filter, and Enter to return to the results.
|
||||
Search includes pipeline name, version, status, outcome, stage and diagnostic;
|
||||
`#123` searches run-ID prefixes. Esc while searching clears the filter without
|
||||
closing the list. The filter survives inspection/back and live list refreshes.
|
||||
Wide terminals
|
||||
show runs and pipelines side by side, with stacked panels on narrow terminals.
|
||||
Run cards show status, duration, start time and the current stage when active.
|
||||
The usage summary is aggregated over all stored history, including retry attempts:
|
||||
@@ -169,10 +175,14 @@ Retry is hidden and rejected while a run is executing or agent cleanup remains
|
||||
active, even if a terminal status was already persisted. Run RPCs report
|
||||
`executing` alongside status so clients can distinguish cleanup from completion.
|
||||
|
||||
The run inspector's upper half shows the actual execution path using the shared
|
||||
pipeline graph renderer and viewport. Visits are numbered, including repeated
|
||||
visits in loops; only recorded routing decisions become edges. No unchosen stage
|
||||
is added to the run path. On small terminals the details take precedence. Press
|
||||
The run inspector's upper half shows the entire graph from the run's immutable
|
||||
pinned version using the shared renderer and viewport. Executed stages and taken
|
||||
routes retain their colors; unexecuted stages, unchosen routes and unreached
|
||||
terminals are dimmed. Queued runs show the full graph before the first visit.
|
||||
Repeated visits remain individually inspectable in the stage sidebar, while the
|
||||
graph highlights every audited route through a loop. On small terminals details
|
||||
take precedence. Older servers without a graph fall back to a matching loaded
|
||||
definition or the recorded execution path, never a different pipeline/version. Press
|
||||
`g` to focus the graph, arrows to pan, and `j/k` or PgUp/PgDn to scroll. Press `g`
|
||||
or Tab to return to details. When not focused, the graph follows the latest visit
|
||||
or selected stage. Existing polling refreshes the graph once per second, and
|
||||
|
||||
Reference in New Issue
Block a user