Document nbshell/nbapi tools for remote build log fetching #2

Closed
opened 2026-06-06 12:19:03 +03:00 by oleks · 1 comment
Owner

The tools nbshell and nbapi are on PATH when the plugin is active, but there's no documentation connecting "my nix build failed on nixbuild.net and I can't see why" to the solution: nbshell 'builds log <id>' or nbapi builds.

Add a section to the plugin CLAUDE.md or README explaining:

  • How to list recent builds: nbapi builds
  • How to get a build log: nbshell 'builds log <BUILD_ID>'
  • How to find the build ID: from the nix error message (it contains the drv path, which can be correlated to the build ID via nbapi builds)
The tools `nbshell` and `nbapi` are on PATH when the plugin is active, but there's no documentation connecting "my nix build failed on nixbuild.net and I can't see why" to the solution: `nbshell 'builds log <id>'` or `nbapi builds`. Add a section to the plugin CLAUDE.md or README explaining: - How to list recent builds: `nbapi builds` - How to get a build log: `nbshell 'builds log <BUILD_ID>'` - How to find the build ID: from the nix error message (it contains the drv path, which can be correlated to the build ID via `nbapi builds`)
Author
Owner

Fixed in main (commits 2f03a04–e167c29): added nbapi build <id> subcommand, documented nbshell 'builds log <id>' in ops.md and nixbuild-usage skill, added routing triggers for build log / remote builder output queries, added .markdownlint-cli2.yaml. Version bumped to 0.2.0.

Fixed in main (commits 2f03a04–e167c29): added `nbapi build <id>` subcommand, documented `nbshell 'builds log <id>'` in ops.md and nixbuild-usage skill, added routing triggers for build log / remote builder output queries, added `.markdownlint-cli2.yaml`. Version bumped to 0.2.0.
oleks closed this issue 2026-06-06 12:52:27 +03:00
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: oleks/claude-plugin-nixbuild#2