bazel

Automate Bazel builds, tests, formatting, and container image pushes via BuildBuddy CLI.

5|Updated Aug 26, 2024
One-click install
npx skills add https://github.com/jomcgi/homelab --skill bazel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bazel
Source: https://github.com/jomcgi/homelab/tree/main/.claude/skills/bazel
Command: npx skills add https://github.com/jomcgi/homelab --skill bazel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build automation and reproducible workflows for large codebases using Bazel via BuildBuddy CLI, simplifying builds, tests, formatting, and image pushes.

Core Features & Use Cases

  • Unified Bazel launcher: Run builds, tests, format, and render manifests through BuildBuddy CLI.
  • Monorepo friendliness: Handles multi-target projects with automatic version management via .bazelversion.
  • CI & deployment workflows: Push container images, render Helm charts, and validate artifacts in CI pipelines.

Quick Start

Format codebase, render manifests, and build targets using BuildBuddy CLI at the repository root.

Frequently Asked Questions about bazel

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

FAQPage Schema
How do I automate Bazel builds and tests in a monorepo with consistent environments?

Automating Bazel builds and tests in a monorepo requires consistent environments and version pinning. This Skill wraps Bazelisk via the BuildBuddy CLI, using a .bazelversion file to ensure reproducible builds across local development and CI pipelines.

What's the best way to push container images and render Helm charts using Bazel in CI?

Pushing container images and rendering Helm charts using Bazel is handled through the BuildBuddy CLI. It automates these deployment workflows alongside build and test targets, enabling seamless artifact validation and image pushes within CI pipelines.

Do I need a .bazelversion file to run Bazel commands through BuildBuddy?

Yes, a .bazelversion file is required to run Bazel commands through BuildBuddy. The Skill relies on this file for version management, using the BuildBuddy launcher to wrap Bazelisk and guarantee reproducible builds across different environments.

Can I format code and render manifests for multi-target Bazel projects locally?

Formatting code and rendering manifests for multi-target Bazel projects is supported locally. The Skill provides a unified launcher through BuildBuddy CLI, allowing you to format the codebase and render manifests directly at the repository root.

Why use BuildBuddy CLI instead of standard Bazel for large codebase build automation?

Using BuildBuddy CLI instead of standard Bazel simplifies build automation for large codebases by providing a unified launcher. It integrates formatting, rendering, and container image workflows while enforcing version pinning for reproducible builds.

Does this approach support rendering manifests and validating artifacts for Bazel targets?

Rendering manifests and validating artifacts for Bazel targets is fully supported. The Skill automates these workflows via BuildBuddy CLI, allowing you to render Helm charts and validate build artifacts alongside standard build and test operations.