Skip to content

bazel

Trust But Verify: Security and Privacy Considerations for Remote Build Execution (RBE) Platforms

For organizations using Bazel and RBE, your build graph is effectively a fingerprint of your product ecosystem and the engineering hierarchy behind it. Depending on the extent to which Bazel and monorepo usage is established within your organization, your Bazel build graph may be composed of interdependent (configured) targets, actions, and artifacts spanning every single dependency, service and test that exists within your codebase.

Other highly valuable sources of metadata related to your codebase that Bazel can produce are JSON trace profiles, effectively structured recordings of what happened during a build and how long it took.

Combined, and observed in time, those two data sources offer insights into release cadence, acquisition targets, engineering headcount, and products potentially being shipped before you are actually ready to ship them. In other words, they are some of the most sensitive data sources an engineering organization produces, and they are routinely treated as exhaust.

Generate BUILD files for new rule sets with Gazelle v2

This post is based on my lightning talk at BazelCon 2026. You can watch the talk on YouTube below.

This talk shows how to support new rule sets by writing an extension with Gazelle's new v2 API, which supports better error handling and dependency resolution. We'll also talk about how Gazelle works with extensions, how to support offline indexing, and how to write extensions in languages other than Go.

Persistent Test Runners: How Persistent Workers for Tests Can Cut Test Times by 46%

This post is based on the BazelCon 2026 talk I gave with Antonio Di Stefano (Frekt.dev). You can watch the recording on YouTube below.

Bazel has used persistent workers for years to make compilation faster. A persistent test runner applies the same idea to tests: keep a long-running test execution process alive and reuse it across multiple tests, instead of paying its warmup cost every time.

BazelCon 2026 Mega-Recap: Scale in the Age of AI, Building the Future of Developer Experience, and Unlimited Coffee

Amsterdam hosted more than 500 build engineers at BazelCon 2026, and one reality framed nearly every discussion: automated coding tools are hammering developer infrastructure.

When autonomous agents generate thousands of pull requests an hour, local laptops lock up and traditional CI pipelines buckle. Across three days of keynotes, workshops, and late-night hallway debates, our team at EngFlow focused on solving that exact crunch. EngFlow showed up with a large presence, including nine technical talks, four sold-out training tracks, and new open-source projects our engineers brought to the community this year. Plus, we had a full-time barista serving everything from espresso to matcha lattes, and a sold out Extreme Scale Party with our partner VirtusLab.

Benchmarking any2bazel - towards more efficient migrations

We’re fond of Bazel, and particularly fond of the capabilities it offers developers. Faster builds, made more efficient through remote execution and caching, made more understandable through declarative configuration, queryability, and precise logging – these deliver benefits and solutions to developers once Bazel’s all set up and integrated into their daily processes.

But it’s a rare developer who enjoys spending their time and effort in build system configuration. Wouldn’t we rather be solving our customers’ problems? And the decision to migrate from an existing build system to Bazel is one that demands consideration of huge trade-offs; the labor and opportunity costs of engineering time spent on migration and adapting internal workflows to a new build system discourage the pursuit of its advantages.

EngFlow is a Cursor Origin launch partner

Bazel makes your builds correct and reproducible. Making them fast, and keeping them fast as your codebase and your team grow, is a different problem. It's the very problem that EngFlow was created to solve. Our team spent years on the adoption side of Bazel, helping companies put it into production, contributing and creating Bazel's core features, and the pattern is almost always the same: teams love what Bazel does for correctness, then run straight into what it costs to operate for speed.

Today, that's much easier to reach. EngFlow, the platform that runs the largest managed Bazel fleet in the world, with over 3 billion build and test actions every week for teams like Arm, Databricks, and Canva, is now one install away for every team on Origin. Read more about this in Origins's announcement on X (Twitter) and Linkedin.

Engineering Developer Tools at Scale: London Build Meetup

EngFlow and Deliveroo (a DoorDash company) recently co-hosted a Build Meetup at Deliveroo's London offices. The event came together thanks to Matt from Deliveroo's engineering management team and Vaibhav from EngFlow, who brought together engineers from Deliveroo, EngFlow, Jane Street, and the local build community.

While talks spanned Bazel, Buck2, and Dune, a central theme emerged: as enterprise codebases grow past tens of millions of lines, the main bottleneck moves from writing code to testing and packaging it.

Here is a breakdown of the three technical presentations from the event.

Introducing any2bazel - an OSS tool for agent-driven migrations to Bazel

Back in June I was sitting on a train to Zurich. The plan was to meet colleagues and work together on figuring out how to migrate CMake projects to Bazel. I was looking forward to chatting with my colleagues in person, but I was not optimistic about the migration process. Truth be told, I was expecting to spend the week walking through the problems parsing the custom CMake language and CMake being Turing complete, maybe even look at a few concrete cases like generated files and configuration flags, finally conclude it couldn't be done, and return home with not much to show. Oh boy was I wrong.

Four War Stories and a Demo: Seattle Build Meetup 2026

Waleed Khan from Stripe presents in Seattle at Uber’s offices

On July 28, 2026, Uber and EngFlow co-hosted a Build Meetup at Uber’s Seattle office. This wouldn’t have been possible without the help of Sergey Balabanov at Uber, who not only presented one of the talks, but also energetically arranged and helped support this event from the Uber side. Thanks again, Sergey!

And, even though nobody planned a theme for this particular meetup (our meetups are holistically focused on “Build, Scale, Investigate”), one showed up anyway. Code is getting cheaper to produce. Uber put it flatly: “AI is a problem, apparently.” Every talk examined some part of the machinery that turns abundant code into software you can trust. Let’s take a look!

Say hello to the new bazel.build website

Today, the new https://bazel.build/ website has finally launched. This is the first step in a larger evolution of Bazel's documentation story. Much of the content remains the same (the eagle-eyed among you may notice a few new pages), but this change marks a new era of Bazel documentation.

What motivated this change?

The Bazel site migration is more than just a fresh coat of paint. One of the underlying motivations for this change is to empower the Bazel community to make more changes to Bazel's documentation. Before the migration, Bazel's website was built on Google documentation infrastructure. While the capabilities of that infrastructure were largely sufficient for Bazel's needs up to now, the contribution experience was not.

Today's https://bazel.build/ is built on Mintlify. With this new platform, each incoming documentation pull request to Bazel is automatically greeted with a preview. For even faster iteration, you can build the site locally. These improvements eliminate guesswork, and better equip contributors to make changes to the Bazel docs with confidence.