Bazel on Alwaldend

Bazel

Mon, 01 Jan 0001 00:00:00 +0000

Advantages

Hermetic builds
Dependency graph
Local build and test cache
Remote cache
Remote execution
Unified API for builds, tasks, and tests

Disadvantages

Additional layer of abstraction and complexity
Weird edge cases and occasional bugs
Lack of support, documentation, and information on the internet
The majority of advantages are irrelevant for the majority of codebases

.bazelrc has variables

%workspace%: Workspace directory

https://bazel.build/run/bazelrc

Local registry module is cached

If you changed a local registry module, but bazel still uses the old version, restart bazel: bazel shutdown

Bazel agent

Mon, 01 Jan 0001 00:00:00 +0000

bazel_agent is the repository Bazel entry point for agents. It keeps the Bazel invocation behind a validated subcommand while consistently applying the agent configuration:

bazel_agent bazel test //path/to/package:all
    ->
bazel test --config=agent //path/to/package:all

bazel is the only Bazel entry point, and it is a validated subcommand. The runner accepts a known Bazel command after the bazel keyword, rejects arbitrary leading arguments, and places --config=agent after the command. Targets, command options, and arguments after the -- separator of a bazel run invocation pass through unchanged. Later options therefore retain Bazel’s normal precedence and can override settings supplied by the agent configuration. The runner resolves bazel from PATH and replaces itself with that process, so signals and the final exit status are not mediated by another wrapper process. Uses of the persistent Bazel server follow the host Codex network policy; the host-bot profile allows loopback so the client-server connection is not blocked.

Bazel agent

Mon, 01 Jan 0001 00:00:00 +0000

bazel_agent is the Bazel entry point for agents working in this repository. It keeps Bazel behind a validated subcommand while consistently applying the agent configuration.

Features

Validated bazel subcommand instead of arbitrary arguments
Applies the agent configuration in the required position
Preserves signals and exit status by replacing itself with the Bazel process
Read-only doctor diagnostics for runner and workspace state

com_github_bazelbuild_bazelisk

Mon, 01 Jan 0001 00:00:00 +0000

Maven Install Gradle Converter

Mon, 01 Jan 0001 00:00:00 +0000

Converts rules_jvm_external maven_install.json lock files into Gradle version catalogs and dependency verification metadata so Bazel-built Android apps can maintain the parallel Gradle build required for F-Droid.

Usage

Use the al_gradle_lock Starlark macro from main/bzl/gradle_lock.bzl in your app’s gradle/BUILD.bazel:

load("//tools/maven_install_gradle_converter:defs.bzl", "al_gradle_lock")

al_gradle_lock(
    name = "update",
    lock_file = "//projects/<app>:maven_lock.json",
    tool = "//tools/maven_install_gradle_converter/cmd/gradle_lock_gen",
)

Run bazel run :update_toml_write to regenerate the checked-in version catalog. The corresponding *_write_test target fails when it goes stale.

Gradle owns verification-metadata.xml because it must record the plugin classpath in addition to the Bazel lock. Regenerate it with:

Bazel on Alwaldend

Bazel

Advantages

Disadvantages

.bazelrc has variables

Local registry module is cached

Bazel agent

Bazel agent

Features

com_github_bazelbuild_bazelisk

Links

Maven Install Gradle Converter

Usage