BuildBuddy Invocation Troubleshoot

Overview

Use this skill to investigate a BuildBuddy invocation end-to-end: locate the invocation, identify failing targets, collect stdout/stderr, determine whether RBE or remote cache was involved, and download build artifacts (raw BES, build logs, execution profiles, cache scorecard).

Workflow (recommended)

0) Preflight: auth + base URL

• Avoid accessing the API key value directly. Check presence by piping to wc and treating any non-empty value as valid, e.g. git config --local buildbuddy.api-key | wc -c.
• If the API key is missing (empty output), ask the user to run bb login and retry.
• Confirm the base URL (default https://app.buildbuddy.io unless self-hosted).
• Collect group_id and (if already known) invocation_id.
• Create a temp working directory (per investigation) and store all downloaded artifacts and API responses there. Reuse cached files to avoid re-calling the API; delete a cached file or set a force flag when you want a fresh response.

Reference request templates live in references/requests.md.

1) Find the invocation ID