Examples
Set up a new React app in this folder with Vite, TypeScript and Mantine. It is the web app of Relay, a CI service for small teams.
Theme: I made it in the theme editor, here is the link: https://themes.mantine.dev/?preset=slate&colors=relay:%233b5bdb&primary=relay&font=Inter&mono-font=JetBrains+Mono&radius=75
Build the pipeline run page, where a developer finds out why a run failed and gets it green again.
Data, hard-coded and generated relative to now:
- the team's 6 projects, each with its default branch and the status of its last run
- run #1842 of the relay-web project on the main branch: commit message, full SHA, author, trigger (push, pull request, schedule or manual), start time, duration and status
- the pipeline of the run: stages Install, Lint, Test, Build and Deploy; each job has a name, status (passed, failed, running, queued, skipped, cancelled), runner, duration, attempts and a log of a few hundred lines split into steps (Set up job, Checkout, Restore cache, Run, Upload artifacts); Test has unit tests in 4 shards, integration tests and end-to-end tests on Chromium and WebKit
- one unit test shard failed on both attempts, so Build and Deploy are skipped; its log ends with the failing assertion and a stack trace
- the test report: about 400 tests in 40 files with durations; 3 failed with an error message and a stack trace, 5 flaky (passed on retry), a few skipped
- the artifacts of the run: name, size and expiry (coverage report, test results, build output)
- the last 20 runs of main: number, status, duration
App shell:
- a sidebar with a project switcher at the top, the pages of the current project (Runs, Pipelines, Artifacts, Environments, Settings) and the team's build minutes used this month at the bottom
- a header with the breadcrumb of the run, a search that jumps to projects and runs from the keyboard (Ctrl+K), a light/dark color scheme toggle (also on Cmd+J) and the user menu
Page:
- a run header: status, run number and the commit message as the title; branch, short SHA that copies the full one, author, trigger, start time ("12 minutes ago", the exact time on hover) and duration; "Re-run failed jobs" as the main action and a menu with Re-run all jobs, Cancel run, Download logs and Copy link
- tabs: Pipeline, Tests (with the number of failed tests) and Artifacts
- Pipeline: the stages as columns of job cards (name, status, duration, attempt), the end-to-end jobs grouped as one matrix job; clicking a job shows its log under the stages
- the log: steps that collapse and expand, each with its duration; monospace lines with line numbers and timestamps; errors and warnings highlighted; a search with the number of matches and next/previous; toggles for timestamps and for wrapping long lines; clicking a line number copies a link to that line; a switch between the job's attempts
- the page opens with the failed job selected and its failing line scrolled into view
- Tests: the totals (passed, failed, flaky, skipped, duration), the failed tests first with their error and stack trace, then a table of all tests with search, a status filter and sorting by duration
- Artifacts: a list with size, expiry and a download button
- next to the pipeline: the run's details (runner, cache hits, environment) and a chart of the durations of the last 20 runs of main, colored by status
- "Re-run failed jobs" starts the failed job again: it queues, then runs with its log lines streaming in and its duration counting up, passes, and Build and Deploy run after it; a notification says when the run passes
- the page works on phones: the sidebar opens from a burger button, the stages stack vertically and nothing scrolls the page sideways; only long log lines scroll inside the log when wrapping is off