skills.rest
sluongng
sluongngCOMMUNITY
Explore all skills by this author →
Website𝕏@sluongngGitHub

buildbuddy-invocation-troubleshoot

Locate BuildBuddy invocations and extract failing targets with logs.

6|Updated Jul 9, 2019
Search Tags:#troubleshooting#logs#artifacts#bazel#invocation#remote-execution#buildbuddy
One-click install
npx skills add https://github.com/sluongng/dotfiles --skill buildbuddy-invocation-troubleshoot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: buildbuddy-invocation-troubleshoot
Source: https://github.com/sluongng/dotfiles/tree/main/config/claude/plugins/buildbuddy/skills/buildbuddy-invocation-troubleshoot
Command: npx skills add https://github.com/sluongng/dotfiles --skill buildbuddy-invocation-troubleshoot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineers troubleshoot BuildBuddy invocations by locating the invocation, identifying failing targets, and collecting stdout/stderr, while discerning whether remote execution or cache metadata caused the failure, and enabling retrieval of build events, profiles, and artifacts for deeper analysis.

Core Features & Use Cases

  • Locate invocations by time window or repository and fetch complete metadata.
  • Identify failing targets and collect stdout/stderr for debugging.
  • Compare remote execution vs remote cache usage and download artifacts for offline review.
  • Use case: When a Bazel build fails in BuildBuddy, quickly surface the failing target, capture logs, and obtain the execution profile to optimize retries.

Quick Start

Investigate a BuildBuddy invocation by locating it, gathering failing targets, and downloading logs and artifacts for review.

Frequently Asked Questions about buildbuddy-invocation-troubleshoot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot a failing Bazel build in BuildBuddy?▼

To troubleshoot a Bazel build failure, locate the specific BuildBuddy invocation, identify the failing targets, and extract stdout and stderr logs to analyze the root cause of the execution or cache failure.

What do I need to diagnose BuildBuddy invocations end-to-end?▼

Diagnosing BuildBuddy invocations end-to-end requires a valid base URL, group_id, invocation_id, and authenticated access to retrieve necessary build events, execution profiles, and artifacts.

How can I find failing targets and collect stdout logs for a Bazel invocation?▼

You can find failing targets and collect stdout logs by locating the specific Bazel invocation within BuildBuddy, which surfaces the failing target metadata and captures the execution output for debugging.

How do I check if remote execution or remote cache caused my Bazel build to fail?▼

To check if remote execution or remote cache caused a Bazel build failure, analyze the invocation metadata to compare remote execution versus remote cache usage and gather associated artifacts.

Can I download execution profiles and artifacts for offline BuildBuddy troubleshooting?▼

Yes, you can download execution profiles and artifacts for offline BuildBuddy troubleshooting by locating the invocation and retrieving the build events and metadata generated during the remote execution.

Related Skills

Explore More Software Engineering Skills→
sluongngsluongng
6

buildbuddy-action-reproduce

Generate a deterministic bb execute replay from a BuildBuddy invocation.

Community
Advanced
leonardoteodorooleonardoteodoroo

bazel-build-optimization

Optimize Bazel configuration, remote execution, and caching for large-scale monorepos.

Community
Advanced
p-o-ke-naep-o-ke-nae

bazel-build-optimization

Optimize Bazel build performance and build graph efficiency in monorepos.

Community
Advanced
sluongngsluongng
6

ask-buddy

Inspect local Bazel and BuildBuddy repository clones to diagnose build issues.

Community
Intermediate