Pipeline run
ProOne pipeline run, stage by stage. Each stage shows what it is doing and how long it has taken, the connectors fill as stages pass, and when one fails the run stops there, opens on the line that failed and offers one button: retry from that stage.
pnpm dlx shadcn@latest add @caliper/pipeline-runDeploy halden-appNot started
main · 4f2a9c1 · Fix retry on declined cards · Maya Chen
- Waiting for the stages before it.
When to use #
Use it for
- CI, deploy and data pipelines where people watch a run finish.
- Any multi-step job that can fail part-way and be resumed.
Skip it when
- A list of many past runs; use the deploys screen or job runs.
Installation #
pnpm dlx shadcn@latest add @caliper/pipeline-run
Adds its 7 files to components/ui/, each with its own stylesheet, and installs their packages. Pro installs with your access token, set up once per project. See Pro access. The first part also adds Caliper UI’s tokens; import them once as in Installation.
Usage #
Import it from your copy of the source. The example behind the preview comes with the source. It is built from PipelineRun and formatElapsed.
import { PipelineRun, formatElapsed } from "@/components/ui/pipeline-run"
The worked example comes with Pro
The 91-line example behind the preview opens here with a Pro or Team licence.
API reference #
PipelineRun
component
formatElapsed
component
No props of its own; it accepts the native props of its root element.
Accessibility #
It exposes status semantics, with aria-hidden, aria-label and aria-pressed kept in step with state. Changes that matter are announced through a live region.
No custom key handling; Tab and the native activation keys do the work.
Motion #
It declares no animation in its component source. Any transition comes from its stylesheet, which uses the duration tokens that collapse to instant under prefers-reduced-motion.