swarm-ui: a builds page for the swarm builder's runs, and the status links to it
/builds lists the builder's recent builds newest first, one card each with how it ended, and opens a failed build's nix tail. /builds?run=<id> opens that build's card and scrolls to it. The swarm-builder commit status now links there instead of to the raw JSON record.
This commit is contained in:
parent
3a7272bdfb
commit
0e77d61a9f
9 changed files with 391 additions and 13 deletions
|
|
@ -86,9 +86,10 @@ newest 100. Both are behind the swarm UI vhost's `admins` gate, and answer 503
|
|||
when the controller has no swarm queue or can't open the bucket, 500 when it
|
||||
can't read it.
|
||||
|
||||
The final status links to `https://<swarm domain>/api/builder/runs/<id>`, so
|
||||
selecting **Details** on a red `swarm-builder` check opens the record, with
|
||||
`nix`'s tail, in the browser. A status has no link when the record wasn't
|
||||
The final status links to `https://<swarm domain>/builds?run=<id>`, the swarm
|
||||
UI's builds page, so selecting **Details** on a red `swarm-builder` check opens
|
||||
that build's card, with `nix`'s tail, in the browser. The raw record stays at
|
||||
`GET /api/builder/runs/<id>`. A status has no link when the record wasn't
|
||||
stored (the controller logs the failed write) or when the controller doesn't
|
||||
serve the swarm vhost (`SWARM_CONTROLLER_PUBLIC_URL` unset). The `pending`
|
||||
status has no link.
|
||||
|
|
|
|||
Loading…
Reference in a new issue