[PiquelChips]

With a build machine (#428), nothing showed whether it was configured or reachable, or where a given build ran. You found out when a deployment failed.

The daemon now keeps the latest check of the build machine's BuildKit daemon, made before each build (#432) or on request, and every surface shows it:

• API: GET /api/v1/system/status includes builder: its address, repository and latest check, only with system:read, like DNS providers. POST /api/v1/system/builder/check checks it now (system:operate), or answers 404 builder_not_configured without a build machine. Each build record has built_on, host or build_machine.
• CLI: piquelctl status shows the build machine and its latest check. piquelctl builder check checks it now and exits 6 while it is unreachable. piquelctl builds list ends each line with on the build machine or on the host.
• Dashboard: the Builds page shows the build machine above the list, warns while it was unreachable, and has Check now. Each build's details say where it was built.

Where a build ran needs no migration: a build machine's image is a repository digest, and the host's is a local image ID (#428). A job run, or a build that reused an image, has no location.

Narrower than the issue

• No builder show: piquelctl status already shows the build machine, so the only new command is builder check.
• Builds page only: the build machine panel is on the Builds page, not on each application's Builds tab.

Testing

• Unit tests for recording a check, the status line in piquelctl, and where a build ran.
• A browser test on the Builds page: an unreachable build machine shows its warning, and Check now updates it.
• On a development instance with a BuildKit daemon: piquelctl status before any check, builder check with the daemon up and stopped, and builds list naming where each build ran.
• I didn't look at the dashboard panel in a browser myself: the development instance's tailnet URL doesn't resolve from the shell I worked in. The browser test above is what covers it.
• cargo nextest for piqueld, piquelctl, piqueld-client and piqueld-core, Clippy for the workspace and the browser target, just openapi-check, just docs.

Stacked on #432. Closes #407. Part of #403.

Note

Written by Claude Opus 5.5 in Claude Code (via T3 Code)

🤖 Generated with Claude Code

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn