# bazel

Bazel is an open-source build and test tool that automates software builds, runs tests, and supports multiple languages and platforms.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Build systems à la trace

DevFeed: [Build systems à la trace](<https://devfeed.tech/articles/build-systems-a-la-trace-143192.md>)

Original publisher: [Read original article](<https://fzakaria.com/2026/11/18/build-systems-a-la-trace>)

Author: Farid Zakaria

Published: 2026-11-18T18:00:00Z

Content type: article

Language: en

Sources: [Farid Zakaria's Blog](<https://devfeed.tech/sources/farid-zakaria-s-blog.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [Build tool](<https://devfeed.tech/topics/build-tool.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>), [make](<https://devfeed.tech/topics/make.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [build-systems](<https://devfeed.tech/tags/build-systems.md>), [trace](<https://devfeed.tech/tags/trace.md>)

### AI overview

genrulify turns a recorded Nix build into Bazel and Buck rules by using Rewind's deterministic VM trace to capture commands, dependencies, environment, file descriptors, and filesystem states. It models each command as a unit of work, tracks successive versions of files to handle in-place changes, and uses MLIR passes to simplify the graph. The initial output is one `genrule` per command, with inputs and outputs made explicit; recorded commands run in a sandbox that recreates their original context. Pattern matching can raise commands into abstractions such as `cc_object`, but these remain macros over genrules and do not change execution semantics. The article reports that Bazel and buck2 produced GNU hello with the same NAR hash served by cache.nixos.org, and argues that the explicit graph enables parallel scheduling even when the original build used `make -j1`. This conversion describes a build after it has run; the excerpt does not establish that future dynamic dependencies are known in advance.

### Source excerpt

As a build systems enthusiast, Build Systems à la Carte is one of my favourite papers. It defines a way to think about build systems that is both precise and surprisingly practical.

## Accelerating development for massive Git repositories

DevFeed: [Accelerating development for massive Git repositories](<https://devfeed.tech/articles/accelerating-development-for-massive-git-repositories-138168.md>)

Original publisher: [Read original article](<https://developers.googleblog.com/accelerating-development-for-massive-git-repositories/>)

Author: The Android ABFS Team

Published: 2026-11-17T18:09:46.914988Z

Content type: article

Language: en

Sources: [Google Developers Blog](<https://devfeed.tech/sources/google-developers-blog.md>)

Topics: [aosp](<https://devfeed.tech/topics/aosp.md>), [Git](<https://devfeed.tech/topics/git.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Gerrit](<https://devfeed.tech/topics/gerrit.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [accelerated](<https://devfeed.tech/tags/accelerated.md>), [acceleration](<https://devfeed.tech/tags/acceleration.md>), [android](<https://devfeed.tech/tags/android.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [cache](<https://devfeed.tech/tags/cache.md>), [content](<https://devfeed.tech/tags/content.md>), [development](<https://devfeed.tech/tags/development.md>), [file](<https://devfeed.tech/tags/file.md>), [filesystem](<https://devfeed.tech/tags/filesystem.md>), [git](<https://devfeed.tech/tags/git.md>), [google](<https://devfeed.tech/tags/google.md>), [open](<https://devfeed.tech/tags/open.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [service](<https://devfeed.tech/tags/service.md>), [source](<https://devfeed.tech/tags/source.md>)

### AI overview

ABFS speeds work on large Android repositories by mounting a virtual filesystem that fetches file contents on demand and shares cached build results. Its Linux kernel module, host daemons, and server use content hashes to store Git objects, workspace changes, and build outputs. CASFS exposes file metadata before downloading bytes; its tap utility records files a build reads or changes, and Ninja-go uses content-addressable caching for Ninja builds. The article reports that agents can mount Android release branches in under eight seconds, check out a tree in under ten seconds, and complete a full build in under ten minutes. These results are from runs on a 64-vCPU GCE VM with the ABFS server in the same cloud network. ABFS is open source; Android Soong/Ninja was its first target, with a Bazel proof of concept and other projects exploring compatibility.

### Source excerpt

Meet Another Build File Service (ABFS), Google's open-source content-addressable filesystem and build cache that cuts Android checkouts to <8s and builds to ~2m.

## Meta Build Systems as Logic Programs

DevFeed: [Meta Build Systems as Logic Programs](<https://devfeed.tech/articles/meta-build-systems-as-logic-programs-136505.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.17672>)

Author: Alex Reinking

Published: 2026-11-16T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [Build tool](<https://devfeed.tech/topics/build-tool.md>), [toolchain](<https://devfeed.tech/topics/toolchain.md>), [CMake](<https://devfeed.tech/topics/cmake.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [LLVM](<https://devfeed.tech/topics/llvm.md>), [Qt](<https://devfeed.tech/topics/qt.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [account](<https://devfeed.tech/tags/account.md>), [android](<https://devfeed.tech/tags/android.md>), [annotations](<https://devfeed.tech/tags/annotations.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [based](<https://devfeed.tech/tags/based.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [build](<https://devfeed.tech/tags/build.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [build-systems](<https://devfeed.tech/tags/build-systems.md>), [builds](<https://devfeed.tech/tags/builds.md>), [can](<https://devfeed.tech/tags/can.md>), [case](<https://devfeed.tech/tags/case.md>), [case-studies](<https://devfeed.tech/tags/case-studies.md>), [cases](<https://devfeed.tech/tags/cases.md>), [central](<https://devfeed.tech/tags/central.md>), [choice](<https://devfeed.tech/tags/choice.md>), [cs-pl](<https://devfeed.tech/tags/cs-pl.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [logic](<https://devfeed.tech/tags/logic.md>), [meta](<https://devfeed.tech/tags/meta.md>), [systems](<https://devfeed.tech/tags/systems.md>)

### AI overview

buildlog models build configuration as relational inference: project objects, flags, libraries, and language standards are derived from sources, dependencies, and requirements, while impure machine probes are isolated to fact discovery. It rejects ambiguous toolchain or package selection, tracks provenance, and keeps author constraints separate from user preferences. Libraries can provide consumer rules, and compiled build tools can have their build-machine configuration inferred. In a Halide case study, buildlog derives build-machine and target configurations in one graph for generators that emit WebAssembly or Android code, where CMake requires nested builds. Evaluation covers eleven case studies across ten projects, with execution and artifact checks; the abstract also reports remaining flag differences and platform limits. Formal guarantees depend on stated finiteness and probe obligations.

### Source excerpt

arXiv:2611.17672v1 Announce Type: cross Abstract: Meta build systems such as CMake, Meson and Bazel derive command graphs from project descriptions, user choices and machine facts. Imperative scripts, search paths and special cases make routine decisions interact poorly: search order can choose compatible packages without an explicit project choice, packagers must patch author flag preferences, and cross-builds need annotations or nested build trees for tools run during the build. Our central insight is to express configuration as relational inference: objects follow from sources, flags and libraries from dependencies, and language standards from transitive requirements. We introduce buildlog, a meta build system whose stratified logical core isolates build derivation from impure environmental probes. It rejects ambiguity in toolchain or package selection and explains derived facts through provenance. Author constraints and user preferences use distinct, statically checked input relations. Libraries can ship consumer rules, including Qt's moc/rcc rules, using the same facts for installed and built code. Using a compiled program in a build rule lets buildlog infer its build-machine configuration. We evaluate buildlog on eleven case studies of ten projects, validating configurations through execution and artifact checks while reporting remaining flag differences and platform limits. In Halide, generators link an LLVM-based compiler and run during the build to emit WebAssembly or Android code; where CMake requires nested builds, buildlog derives build-machine and target-platform configurations in one graph. A supporting formal account establishes termination, within-round probe-order independence, and agreement between fresh and validated cached runs under explicit finiteness and probe obligations. The results show that confining impurity to fact discovery yields a small, uniform and explainable configuration semantics.

## How We Stabilized a Bazel CI Runner by Fixing Resource Limits and Container Cleanup

DevFeed: [How We Stabilized a Bazel CI Runner by Fixing Resource Limits and Container Cleanup](<https://devfeed.tech/articles/how-we-stabilized-a-bazel-ci-runner-by-fixing-resource-limits-and-container-cleanup-114855.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-we-stabilized-a-bazel-ci-runner-by-fixing-resource-limits-and-container-cleanup?source=rss>)

Author: Daniil Romashov

Published: 2026-11-03T15:21:51Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [cgroups](<https://devfeed.tech/topics/cgroups.md>), [scheduling](<https://devfeed.tech/topics/scheduling.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [builds](<https://devfeed.tech/tags/builds.md>), [c-plus-plus](<https://devfeed.tech/tags/c-plus-plus.md>), [cache](<https://devfeed.tech/tags/cache.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [cfs](<https://devfeed.tech/tags/cfs.md>), [cgroups](<https://devfeed.tech/tags/cgroups.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cleanup](<https://devfeed.tech/tags/cleanup.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [container](<https://devfeed.tech/tags/container.md>), [container-cleanup](<https://devfeed.tech/tags/container-cleanup.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [containers](<https://devfeed.tech/tags/containers.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [cpus](<https://devfeed.tech/tags/cpus.md>), [docker](<https://devfeed.tech/tags/docker.md>), [gitlab-runner](<https://devfeed.tech/tags/gitlab-runner.md>), [limits](<https://devfeed.tech/tags/limits.md>), [monorepo](<https://devfeed.tech/tags/monorepo.md>), [oom](<https://devfeed.tech/tags/oom.md>), [oom-killer](<https://devfeed.tech/tags/oom-killer.md>), [resource](<https://devfeed.tech/tags/resource.md>), [runner](<https://devfeed.tech/tags/runner.md>)

### AI overview

Bazel CI jobs were being OOM-killed because a runner with 6 cores and 62 GiB of memory had no per-job cgroup limits, while jobs acted on stale configuration promising 5 CPUs and 24 GiB each. After three days of tuning, the runner stabilized at five jobs with a hard 11 GiB memory cap per job; Bazel's local resource estimate was set below that cap, using measured 6.68 GiB RSS rather than an 11.37 GiB working set that included reclaimable page cache. Hard CPU quotas caused heavy throttling, so CPU allocation was made fair while the memory cap remained strict. The team also moved linting and review tasks to a lighter runner. Separately, integration-test helper containers launched through the Docker SDK outlived canceled CI jobs because cleanup in finally blocks was skipped and the containers lacked the labels used by garbage collection. Adding the Testcontainers label at each launch site made them eligible for cleanup. The account emphasizes verifying runner capacity and labeling all containers; it describes one environment and does not establish a universal configuration.

### Source excerpt

Bazel builds kept getting OOM-killed on a CI runner whose config promised 25 CPUs it did not have. How hard cgroup caps and three days of retuning settled the m

## Linux Foundation Newsletter: October 2026

DevFeed: [Linux Foundation Newsletter: October 2026](<https://devfeed.tech/articles/linux-foundation-newsletter-october-2026-93097.md>)

Original publisher: [Read original article](<https://www.linuxfoundation.org/blog/linux-foundation-newsletter-october-2026>)

Author: andrewb@proximabiz.com (The Linux Foundation)

Published: 2026-10-21T18:00:00Z

Content type: news

Language: en

Sources: [Linux Foundation](<https://devfeed.tech/sources/linux-foundation-blog.md>)

Topics: [linux foundation](<https://devfeed.tech/topics/linux-foundation.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [LF Research](<https://devfeed.tech/topics/lf-research.md>), [lf education](<https://devfeed.tech/topics/lf-education.md>), [openssf](<https://devfeed.tech/topics/openssf.md>), [LF Europe](<https://devfeed.tech/topics/lf-europe.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [jupyter](<https://devfeed.tech/topics/jupyter.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [blog](<https://devfeed.tech/tags/blog.md>), [careers](<https://devfeed.tech/tags/careers.md>), [certifications](<https://devfeed.tech/tags/certifications.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [cybersecurity-awareness-month](<https://devfeed.tech/tags/cybersecurity-awareness-month.md>), [cybersecurity-training](<https://devfeed.tech/tags/cybersecurity-training.md>), [data-infrastructure](<https://devfeed.tech/tags/data-infrastructure.md>), [education](<https://devfeed.tech/tags/education.md>), [embedded-systems](<https://devfeed.tech/tags/embedded-systems.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [lf-europe](<https://devfeed.tech/tags/lf-europe.md>), [lf-events](<https://devfeed.tech/tags/lf-events.md>), [lf-research](<https://devfeed.tech/tags/lf-research.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-blog](<https://devfeed.tech/tags/linux-blog.md>), [linux-foundation](<https://devfeed.tech/tags/linux-foundation.md>), [newsletter](<https://devfeed.tech/tags/newsletter.md>), [october](<https://devfeed.tech/tags/october.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [open-source-summit](<https://devfeed.tech/tags/open-source-summit.md>), [project-news](<https://devfeed.tech/tags/project-news.md>), [projects](<https://devfeed.tech/tags/projects.md>), [tech-talent](<https://devfeed.tech/tags/tech-talent.md>)

### AI overview

The October 2026 Linux Foundation newsletter highlights new infrastructure initiatives, research, and project releases. AWS became a Platinum Member; the new BUILD Foundation offers Bazel-dependent organizations a way to fund the ecosystem and help direct it; and OpenGrid sets shared architecture and interoperability standards for power-grid planning tools. FINOS says OSERA is operational, backed by five global banks, with its first release providing secure updates for more than 50 Spring and Java libraries. Research highlights include a study of OSPOs and AI governance and a report finding openly governed data platforms are gaining ground as AI workloads grow. Project updates span agentic AI, security, energy, networking, and developer tools, including OpenSearch 3.9's vector-search and observability features and VOLTHA 2.16's event-driven failure indications and per-device telemetry. The newsletter also advertises limited-time LF Education discounts.

### Source excerpt

Welcome to the October 2026 edition of the Linux Foundation Newsletter Cybersecurity Awareness Month is ending, and LF Education is discounting training for a limited time. You cansave 40% on eligible cybersecurity training and certifications, and you can save 35% on other training and certifications. A THRIVE-ONE Annual subscription is 30% off. This month's biggest announcements include a new Platinum Member and two new foundations. AWSbecame a Platinum Member of the Linux Foundation, after more than a decade of taking part in LF projects. The Linux Foundation launched theBUILD Foundation, which gives organizations that depend on Bazel a formal way to fund the project and help set its direction. The Linux Foundation also launchedOpenGrid, which sets shared software architecture and interoperability standards so that power grid planning tools can work together. In addition, FINOS announced thatOSERA is now operating, with support from Deutsche Bank, Goldman Sachs, Morgan Stanley, NatWest, and RBC. The first OSERA release includes secure updates for more than 50 widely used Spring and Java libraries. LF Research published nine reports this month.35 Years of Linux follows the kernel from a hobby project to the software that now runs on 4 billion Android devices, more than 200 million servers, and all 500 of the world's top supercomputers. The 9th annualState of OSPOs study looks at how open source program offices are handling AI governance. The2026 Open Data Infrastructure Report finds that openly governed data platforms are gaining ground as more organizations run AI workloads. You'll also find a recap of the Linux Foundation Member European Forum in Prague and details on the LF Education Learning Lounge at KubeCon + CloudNativeCon North America. The project news covers agentic AI, finance, energy, networking, security, and embedded systems. >> Read on for even more news, research, and opportunities from across the Linux Foundation.

## Taming Bazel Dependency Conflicts: An Android Case Study

DevFeed: [Taming Bazel Dependency Conflicts: An Android Case Study](<https://devfeed.tech/articles/taming-bazel-dependency-conflicts-an-android-case-study-85771.md>)

Original publisher: [Read original article](<https://proandroiddev.com/taming-bazel-dependency-conflicts-an-android-case-study-44b7926839be?source=rss----c72404660798---4>)

Author: Taufik Amaryansyah

Published: 2026-10-12T23:38:04Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [Dependency management](<https://devfeed.tech/topics/dependency-management.md>), [Gradle](<https://devfeed.tech/topics/gradle.md>), [Maven](<https://devfeed.tech/topics/maven.md>), [Android](<https://devfeed.tech/topics/android.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [case-study](<https://devfeed.tech/tags/case-study.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [dependency-management](<https://devfeed.tech/tags/dependency-management.md>), [gradle](<https://devfeed.tech/tags/gradle.md>)

### AI overview

While updating an Android app to the Compose BOM 2024.12.01, the author hit conflicting AndroidX versions: `activity-compose:1.7.0` requested Compose UI 1.0.1, while the BOM supplied 1.7.6. The article contrasts Gradle's default newest-version selection with Bzlmod's minimal version selection, which chooses the earliest version explicitly required by the graph and does not automatically upgrade to a newer available release. The author says `version_conflict_policy = "pinned"` only pins successfully resolved versions; it does not fix the conflict. Their workaround is to run `bazel clean --expunge bazel run @maven//:pin`, save and inspect the full log for the conflicting artifact, add a `maven.artifact` version override before `maven.install`, then rerun pinning and repeat for other conflicts. They chose the newest listed version first, trying the next newest if errors remained. After several overrides, pinning and the app build succeeded. The author notes that updating Bazel rules can require configuration and Bazel version changes; the excerpt does not give the complete override configuration.

### Source excerpt

Illustration Generated by Gemini For many developers, "dependency conflict" is a phrase that instantly causes a headache. This is especially true when moving from a familiar ecosystem like Gradle to a powerful but complex tool like Bazel. A while back, I wrote about my experience building an Android app with Bazel (You can read about it here: Building a Modern Android Music Player App with Bazel...). Recently, I decided to update some libraries in that project, most notably by moving to the Compose BOM (androidx.compose:compose-bom:2024.12.01). 🧨 The Problem Begins: A Simple Library Update I updated my MODULE.bazel file with the new dependencies. The initial attempt looked something like this: https://medium.com/media/ab6ac611fb4ff73c1120f2dba1a8df3e/href I ran the build, and... it failed. I was greeted by a long, cryptic error log, which boiled down to a classic dependency conflict. Here's just a small snippet of the dependency graph hell: At its core, the problem was familiar. For example, looking at the log: androidx.activity:activity-compose:1.7.0 (which I was using) explicitly wants androidx.compose.ui:ui:1.0.1. But the new Compose BOM (2024.12.01) was pulling in androidx.compose.ui:ui:1.7.6 (a much newer version). This threw me for a loop. In my time with Gradle, I rarely faced conflicts this severe. Gradle usually seems "smart" enough to just pick the newest version and move on. 🧠 Understanding the "Why": Gradle vs. Bazel After some digging, I realized the fundamental difference lies in how these build tools manage versions. 1. Gradle: "Newest Version Wins" (By Default) Gradle, by default, uses a "Newest Version Selection" strategy. If it encounters a conflict, it simply picks the newest version of the dependency available in the graph. A -> C v1.0 B -> C v2.0 Gradle's Result: C v2.0 (Chosen automatically) 2. Bazel (Bzlmod): "Minimal Version Selection" (MVS) Bazel, with the introduction of Bzlmod, adopts the "Minimal Version Selection" (MVS) algorithm, which is als

## How AI Changes Ownership of the CI Feedback-and-Repair Loop

DevFeed: [How AI Changes Ownership of the CI Feedback-and-Repair Loop](<https://devfeed.tech/articles/the-feedback-loop-is-moving-out-of-ci-55876.md>)

Original publisher: [Read original article](<https://swamp-club.com/feed/p/7bb95d0a-9c27-49e8-ab1c-47ecc2f64271/go>)

Author: stack72

Published: 2026-09-03T16:35:31Z

Content type: article

Language: en

Sources: [Swamp Club Feed](<https://devfeed.tech/sources/swamp-club-feed.md>)

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Google](<https://devfeed.tech/topics/google.md>), [monorepo](<https://devfeed.tech/topics/monorepo.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [version-control](<https://devfeed.tech/topics/version-control.md>), [service](<https://devfeed.tech/topics/service.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [building-with-ai](<https://devfeed.tech/tags/building-with-ai.md>), [ci](<https://devfeed.tech/tags/ci.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [google](<https://devfeed.tech/tags/google.md>), [monorepo](<https://devfeed.tech/tags/monorepo.md>), [test-automation](<https://devfeed.tech/tags/test-automation.md>), [version-control](<https://devfeed.tech/tags/version-control.md>)

### AI overview

The article revisits an argument about CI after comparing it with Google's long-standing separation of test verification and merge coordination. It argues that the important change is who owns the feedback-and-repair loop when code-producing systems can implement, observe failures, and repair changes.

### Source excerpt

Paul Hammant pointed out that Google separated verification from merge coordination more than fifteen years ago. He was right. What actually changed is who owns the feedback-and-repair loop -- and that shifts what CI needs to be.

## Bazel Q2 2026 Community Update

DevFeed: [Bazel Q2 2026 Community Update](<https://devfeed.tech/articles/bazel-q2-2026-community-update-53179.md>)

Original publisher: [Read original article](<https://blog.bazel.build/2026/07/07/bazel-q2-2026-community-update.html>)

Published: 2026-07-07T00:00:00Z

Content type: release

Language: en

Sources: [Bazel Blog](<https://devfeed.tech/sources/bazel-blog.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [releases](<https://devfeed.tech/topics/releases.md>), [CLion](<https://devfeed.tech/topics/clion.md>), [debugging](<https://devfeed.tech/topics/debugging.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [community-update](<https://devfeed.tech/tags/community-update.md>), [conference](<https://devfeed.tech/tags/conference.md>), [product-updates](<https://devfeed.tech/tags/product-updates.md>), [releases](<https://devfeed.tech/tags/releases.md>)

### AI overview

The Bazel Q2 2026 community update covers BazelCon 2026, its call for proposals and training day, upcoming Bazel 9.2.0 and 8.8.0 releases, and updates to the Bazel for CLion plugin, including changes to debug configurations and source-file configuration switching.

### Source excerpt

Announcements BazelCon 2026 - details The Details at a Glance: What: BazelCon 2026 Where: Postillion Hotel & Convention Centre Amsterdam, Netherlands When: October 13-15, 2026 October 13th - Training Day October 14th & 15th - 2 Conference days filled with technical sessions, Birds of a Feather and networking with the best in the field. Get your ticket and find all the details via the BazelCon website! For the most up to date BazelCon news and updates, follow the Bazel X account and the #bazelcon Bazel Slack channel. Call for Proposals This year, we received a tremendous 170 talk submissions! A huge thank you to everyone who took the time to submit a proposal. The Review Committee is already diligently reviewing them to curate the 2026 schedule. Speaker confirmations will be sent out on July 20th, and we will announce the schedule a few days later. If your submission isn't selected this year, we highly encourage you to apply again next time - and we sincerely applaud your willingness to share your stories with the community! BazelCon Training Day Following last year's success, we are bringing back Training Day right before the main conference. The schedule features two parallel tracks with four sessions each, allowing you to choose one session per time slot. You can select your sessions when you secure your BazelCon ticket on the website. Already registered? You can easily edit your existing registration to secure a spot in the trainings of your choice. Please Note: Seats are limited. If your plans change and you can no longer attend, please free up your spot so someone on the waitlist can take your place. Product Updates Upcoming Bazel releases Bazel 9.2.0 is expected to release on 2026-07-09. RC1 was released on 2026-06-25. Bazel 8.8.0 is expected to release on 2026-07-15. Please send cherry-pick PRs against the release-8.8.0 branch before the RC1 cutoff on 2026-07-08. Q2 releases 9.1.0 was released in April '26, followed by patch 9.1.1. 8.7.0 was released in May '

## The Best Platforms for Monorepo Deployments in 2026

DevFeed: [The Best Platforms for Monorepo Deployments in 2026](<https://devfeed.tech/articles/the-best-platforms-for-monorepo-deployments-in-2026-95505.md>)

Original publisher: [Read original article](<https://blog.railway.com/p/best-monorepo-deployment-platforms-2026>)

Author: Angelo Saraceno

Published: 2026-05-26T00:00:00Z

Content type: article

Language: en

Sources: [Railway](<https://devfeed.tech/sources/railway.md>)

Topics: [monorepo](<https://devfeed.tech/topics/monorepo.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [platform engineering automation](<https://devfeed.tech/topics/platform-engineering-automation.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [2021](<https://devfeed.tech/tags/2021.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [abstraction](<https://devfeed.tech/tags/abstraction.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [best](<https://devfeed.tech/tags/best.md>), [build](<https://devfeed.tech/tags/build.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [monorepo](<https://devfeed.tech/tags/monorepo.md>), [net](<https://devfeed.tech/tags/net.md>), [nx](<https://devfeed.tech/tags/nx.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [railway](<https://devfeed.tech/tags/railway.md>), [render](<https://devfeed.tech/tags/render.md>), [turborepo](<https://devfeed.tech/tags/turborepo.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

The article argues that monorepo tooling has two complementary layers: build orchestrators determine which packages need rebuilding and testing, while deploy platforms run the resulting services. It recommends choosing one from each category rather than treating them as substitutes. For builds, Turborepo is presented as a simpler fit for JS/TS repositories, Nx or Moonrepo for polyglot needs, and Bazel for very large or hermetic-build environments at substantial operating cost. For deployment, Railway offers per-service paths and shared variables with usage-based billing; Render uses YAML blueprints and fixed-size pricing; Vercel fits frontend-heavy repositories but is described as less suitable for long-running backend services; Northflank adds Kubernetes-style controls and BYOC with more learning overhead. The article suggests using GitHub Actions for small repositories, and weighing service count, language mix, workload type, billing predictability, BYOC, and YAML tolerance when selecting a stack.

### Source excerpt

Monorepo discussions conflate two distinct categories: build orchestration (Turborepo, Nx, Bazel) and deploy platforms (Railway, Vercel, Render). A ranking that separates them and explains how they fit together.

## Benchmark: Bazel builds 39.7x faster on Avrea than GitHub Actions

DevFeed: [Benchmark: Bazel builds 39.7x faster on Avrea than GitHub Actions](<https://devfeed.tech/articles/benchmark-bazel-builds-39-7x-faster-on-avrea-than-github-actions-122841.md>)

Original publisher: [Read original article](<https://avrea.com/blog/bazel-ci-benchmark>)

Author: Leo Lännenmäki

Published: 2026-04-21T00:00:00Z

Content type: news

Language: en

Sources: [Avrea Blog](<https://devfeed.tech/sources/avrea-blog.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Benchmark](<https://devfeed.tech/topics/benchmark.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub](<https://devfeed.tech/topics/github.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [builds](<https://devfeed.tech/tags/builds.md>), [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [ephemeral](<https://devfeed.tech/tags/ephemeral.md>), [faster](<https://devfeed.tech/tags/faster.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [iso-27001](<https://devfeed.tech/tags/iso-27001.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [remote](<https://devfeed.tech/tags/remote.md>)

### AI overview

In this Bazel benchmark, Avrea completed the no-cache build in 14m 4s versus 37m 10s on GitHub Actions, and a warm run using Avrea's co-located Bazel remote cache took 56 seconds. The article attributes the 2.6x no-cache result to higher reported single-core performance and disk writes on Avrea's 2 vCPU runner; caching skips unchanged actions by retrieving outputs keyed to input hashes, producing the reported 39.7x overall speedup. The GitHub Actions run had no comparable built-in cache, so the cached comparison uses Avrea's remote cache.

### Source excerpt

37m 10s on GitHub Actions. 14m 4s on Avrea without cache. 56 seconds with cache. That's 2.6x from the hardware, 39.7x once caching kicks in.

## Bazel Q1 2026 Community Update

DevFeed: [Bazel Q1 2026 Community Update](<https://devfeed.tech/articles/bazel-q1-2026-community-update-53178.md>)

Original publisher: [Read original article](<https://blog.bazel.build/2026/04/08/bazel-q1-2026-community-update.html>)

Published: 2026-04-08T00:00:00Z

Content type: news

Language: en

Sources: [Bazel Blog](<https://devfeed.tech/sources/bazel-blog.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [Maintainers](<https://devfeed.tech/topics/maintainers.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [community-update](<https://devfeed.tech/tags/community-update.md>), [conference](<https://devfeed.tech/tags/conference.md>), [linux](<https://devfeed.tech/tags/linux.md>), [maintainers](<https://devfeed.tech/tags/maintainers.md>)

### AI overview

The Bazel Q1 2026 community update announces BazelCon 2026 in Amsterdam, including its dates, training and conference programming, registration timing, and call for proposals. It also mentions the expected Bazel 9.1.0 release and the related cherry-pick deadline.

### Source excerpt

Announcements Mark Your Calendars: BazelCon 2026 is Heading to Amsterdam! Get ready to build at scale in the heart of Europe. We are thrilled to announce that BazelCon 2026 will be taking place in the vibrant city of Amsterdam from October 13th-15th. Whether you're a seasoned build engineer or just starting your journey with monorepos and hermeticity, this is the place to be. Expect three days of deep-dive technical sessions, hands-on workshops, and the chance to connect with the global community of maintainers and power users. The Details at a Glance: What: BazelCon 2026 Where: Postillion Hotel & Convention Centre Amsterdam, Netherlands When: October 13-15, 2026 October 13th - Training Day October 14th & 15th - 2 Conference days filled with technical sessions, Birds of a Feather and networking with the best in the field. Registration opens April 22nd - register via the BazelCon website! For the most up to date BazelCon news and updates, follow the Bazel X account and the #bazelcon Bazel Slack channel. Call for Proposals Do you have a Bazel story to tell? We want to hear how you're using Bazel to solve complex problems, whether you're optimizing massive monorepos or building custom rules for your team. Sharing your real-world wins and lessons learned helps the entire community grow, so don't hesitate to submit a proposal regardless of your experience level. CFP Opens: April 22 CFP Closes: June 21 Review Period: June 22 - July 8 Speaker Notifications: July 20 Schedule Announcement: July 22 The CfP submission form will be available via the BazelCon website. Want to become a Sponsor of BazelCon 2026? Hosted by the Bazel Community in partnership with The Linux Foundation, BazelCon is the premier annual event for build enthusiasts, maintainers, and contributors to connect in an inclusive environment. Sponsoring BazelCon 2026 puts your company right in front of the best build and platform engineers in the business. It is a great way to show your support for the community,

## Introducing Chainguard OS Packages: Secure ingredients for custom container builds

DevFeed: [Introducing Chainguard OS Packages: Secure ingredients for custom container builds](<https://devfeed.tech/articles/introducing-chainguard-os-packages-secure-ingredients-for-custom-container-builds-13112.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/introducing-chainguard-os-packages>)

Published: 2026-03-17T00:00:00Z

Content type: article

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [chainguard](<https://devfeed.tech/topics/chainguard.md>), [chainguard os](<https://devfeed.tech/topics/chainguard-os.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Docker Hardened Images](<https://devfeed.tech/topics/docker-hardened-images.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Dockerfile](<https://devfeed.tech/topics/dockerfile.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [chainguard sboms](<https://devfeed.tech/topics/chainguard-sboms.md>), [APK](<https://devfeed.tech/topics/apk.md>)

Tags: [apk](<https://devfeed.tech/tags/apk.md>), [apko](<https://devfeed.tech/tags/apko.md>), [automation](<https://devfeed.tech/tags/automation.md>), [base-images](<https://devfeed.tech/tags/base-images.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [chainguard-containers](<https://devfeed.tech/tags/chainguard-containers.md>), [chainguard-libraries](<https://devfeed.tech/tags/chainguard-libraries.md>), [chainguard-os](<https://devfeed.tech/tags/chainguard-os.md>), [chainguard-os-packages](<https://devfeed.tech/tags/chainguard-os-packages.md>), [chainguard-packages](<https://devfeed.tech/tags/chainguard-packages.md>), [chainguard-sboms](<https://devfeed.tech/tags/chainguard-sboms.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [cve](<https://devfeed.tech/tags/cve.md>), [dockerfiles](<https://devfeed.tech/tags/dockerfiles.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [sboms](<https://devfeed.tech/tags/sboms.md>), [secure-software-packages](<https://devfeed.tech/tags/secure-software-packages.md>), [software-packages](<https://devfeed.tech/tags/software-packages.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [zero-cve-packages](<https://devfeed.tech/tags/zero-cve-packages.md>)

### AI overview

Chainguard introduces Chainguard OS Packages, a service providing continuously maintained, enterprise-grade packages and base images for teams that build custom container images. Customers retain control over image composition and build tooling while Chainguard handles package sourcing, rebuilding, vulnerability remediation, and SBOM generation.

### Source excerpt

Chainguard OS Packages are enterprise-grade, zero-CVE packages and base images built and continuously maintained in the Chainguard Factory.

## Dependabot version updates now support Bazel

DevFeed: [Dependabot version updates now support Bazel](<https://devfeed.tech/articles/dependabot-version-updates-now-support-bazel-72122.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2025-12-16-dependabot-version-updates-now-support-bazel>)

Author: Allison

Published: 2025-12-16T16:45:50Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [Dependabot](<https://devfeed.tech/topics/dependabot.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [dependabot](<https://devfeed.tech/tags/dependabot.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [reproducible-builds](<https://devfeed.tech/tags/reproducible-builds.md>), [updates](<https://devfeed.tech/tags/updates.md>)

### AI overview

Dependabot version updates now support Bazel projects using either Bzlmod or WORKSPACE. It detects dependency declarations, checks the Bazel Central Registry, regenerates lockfiles, and opens pull requests with updated declarations, release notes, and compatibility information. Requirements include Bazel 7, 8, or 9 and a MODULE.bazel or WORKSPACE file at the repository root.

### Source excerpt

Developers can now use Dependabot to automatically keep their Bazel dependencies up to date. For projects that use Bazel--either Bzlmod or WORKSPACE--Dependabot version updates can now ensure dependencies stay current...

## The Cost of Speed: A Battle against Cost, Debt, and Diverging Systems

DevFeed: [The Cost of Speed: A Battle against Cost, Debt, and Diverging Systems](<https://devfeed.tech/articles/the-cost-of-speed-a-battle-against-cost-debt-and-diverging-systems-56799.md>)

Original publisher: [Read original article](<https://engineering.mercari.com/en/blog/entry/20251215-the-cost-of-speed-a-battle-against-cost-debt-and-diverging-systems/>)

Author: ShindeSnehal

Published: 2025-12-16T09:00:49Z

Content type: opinion

Language: en

Sources: [Mercari Engineering](<https://devfeed.tech/sources/mercari-engineering.md>)

Topics: [systems](<https://devfeed.tech/topics/systems.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>), [Cloud Run](<https://devfeed.tech/topics/cloud-run.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [gRPC](<https://devfeed.tech/topics/grpc.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>), [monorepo](<https://devfeed.tech/topics/monorepo.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Serverless](<https://devfeed.tech/topics/serverless.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [backend](<https://devfeed.tech/tags/backend.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [cloud-run](<https://devfeed.tech/tags/cloud-run.md>), [costs](<https://devfeed.tech/tags/costs.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [grpc](<https://devfeed.tech/tags/grpc.md>), [latency](<https://devfeed.tech/tags/latency.md>), [maintenance](<https://devfeed.tech/tags/maintenance.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [monorepo](<https://devfeed.tech/tags/monorepo.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [product-engineering](<https://devfeed.tech/tags/product-engineering.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [systems](<https://devfeed.tech/tags/systems.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

A Mercari Product Engineering director describes how the Shops Enabling Team worked to merge two heterogeneous systems after an architecture optimized for rapid delivery led to rising operating costs, latency, complexity, and maintenance challenges.

### Source excerpt

This post is for Day 16 of the Mercari Advent Calendar 2025. Introduction Hello, my name is Sneha. I am a Director in Product Engineering, managing the Ads and Shops product engineering teams. I want to share a personal journey--not just of systems and code, but of a "perfect squad" known as the Shops Enabling [...]

## Shops Monorepo Five Years Later: A Tale of Bazel and Cursor

DevFeed: [Shops Monorepo Five Years Later: A Tale of Bazel and Cursor](<https://devfeed.tech/articles/shops-monorepo-five-years-later-a-tale-of-bazel-and-cursor-56791.md>)

Original publisher: [Read original article](<https://engineering.mercari.com/en/blog/entry/20251202-shops-monorepo-five-years-later-a-tale-of-bazel-and-cursor/>)

Author: MoreiraJasper

Published: 2025-12-03T11:00:31Z

Content type: article

Language: en

Sources: [Mercari Engineering](<https://devfeed.tech/sources/mercari-engineering.md>)

Topics: [monorepo](<https://devfeed.tech/topics/monorepo.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Code](<https://devfeed.tech/topics/code.md>), [cursor](<https://devfeed.tech/topics/cursor.md>), [Go Language](<https://devfeed.tech/topics/go-language.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [observability](<https://devfeed.tech/topics/observability.md>), [azure container apps](<https://devfeed.tech/topics/azure-container-apps.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [go](<https://devfeed.tech/tags/go.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [monorepo](<https://devfeed.tech/tags/monorepo.md>), [observability](<https://devfeed.tech/tags/observability.md>)

### AI overview

Mercari Shops describes five years of operating a Bazel-powered monorepo across a microservices architecture. The team discusses technical debt, dependency conflicts, incompatible build systems, and the effort to unify builds across backend, frontend, and protocol buffers. It also reports that the standardized repository made it easier to adopt Cursor and Claude Code.

### Source excerpt

This post is for Day 3 of the Mercari Advent Calendar 2025. Introduction Hi, I'm Jazz from the Mercari Shops Enabling team. Our team handles a variety of responsibilities in Mercari Shops, ranging from backend, to observability, all the way to CI/CD. Our mission is to ensure the engineers who work on Mercari features have [...]

## Bazel rule extensions

DevFeed: [Bazel rule extensions](<https://devfeed.tech/articles/bazel-rule-extensions-25413.md>)

Original publisher: [Read original article](<https://smileykeith.com/2025/10/31/bazel-rule-extensions/>)

Author: Keith Smiley

Published: 2025-10-31T17:00:00Z

Content type: article

Language: en

Sources: [Keith Smiley](<https://devfeed.tech/sources/keith-smiley.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [Inheritance](<https://devfeed.tech/topics/inheritance.md>), [extend](<https://devfeed.tech/topics/extend.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [class](<https://devfeed.tech/tags/class.md>), [custom](<https://devfeed.tech/tags/custom.md>), [existing](<https://devfeed.tech/tags/existing.md>), [extend](<https://devfeed.tech/tags/extend.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [inheritance](<https://devfeed.tech/tags/inheritance.md>), [object-oriented-programming](<https://devfeed.tech/tags/object-oriented-programming.md>), [providers](<https://devfeed.tech/tags/providers.md>), [use-case](<https://devfeed.tech/tags/use-case.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>)

### AI overview

Bazel 8.0 rule extensions let a new rule inherit an existing rule, call its implementation with `ctx.super()`, then alter providers, add a transition, or attach aspects. The excerpt shows post-processing a rule's output with a sort action; normalizing macOS and Linux debug outputs into one `OutputGroupInfo` group; adding a Python version transition to `py_wheel`; and applying Apple platform transitions to Swift libraries. The Swift example requires transition attributes and can use `select()` in a macro to preserve tvOS dependencies. Limitations include restricted attribute overrides, the requirement that `parent` be a rule rather than a macro, and difficulty modifying existing actions such as adding `-ftime-trace` output.

### Source excerpt

One of Bazel's best features is being able to easily write custom rules specific to your project. This is great for many use cases, but when what you really want is to enhance the behavior of existing rules, historically your options have been limited. What you would often do is wrap the existing rule in a macro, and add some number of custom rules to try and achieve the desired effect. When really what you want is to edit the existing rule, without having to re-implement all of its functionality (or maintain a fork). With Bazel 8.0, Googlers added a few new ways to extend existing rules that can help with this use case. In this post we will look at the aptly named rule extensions feature and some practical use cases I have found for it. Basic rule extensions Rule extensions allow you to inherit the behavior of an existing rule, similar to class inheritance in object-oriented programming. Importantly you can make a few modifications to augment the behavior of the rule to your liking. Let's say you have a rule that concatenates the given srcs: def _foo_impl(ctx): output = ctx.actions.declare_file("output.txt") ctx.actions.run_shell( inputs = ctx.files.srcs, outputs = [output], command = "cat {} > {}".format(" ".join([src.path for src in ctx.files.srcs]), output.path), ) return [DefaultInfo(files = depset([output]))] foo = rule( implementation = _foo_impl, attrs = { "srcs": attr.label_list(allow_files = True), }, ) Now let's assume in your project, you want the output file to be sorted. If you own the original rule you could of course change _foo_impl to handle that for you, but if you are relying on a more complex upstream rule, you may not have that luxury. Here's how we can extend this to post-process the file it produces: def _bar_impl(ctx): providers = ctx.super() # Invoke 'foo' and get the providers # NOTE: This assumes there's always only the provider we want. original_output = providers[0].files.to_list()[0] new_output = ctx.actions.declare_file("new_output.tx

## Understanding Apple Debug Info

DevFeed: [Understanding Apple Debug Info](<https://devfeed.tech/articles/understanding-apple-debug-info-25412.md>)

Original publisher: [Read original article](<https://smileykeith.com/2025/09/21/understanding-apple-debug-info/>)

Author: Keith Smiley

Published: 2025-09-21T17:00:00Z

Content type: article

Language: en

Sources: [Keith Smiley](<https://devfeed.tech/sources/keith-smiley.md>)

Topics: [Developer Tools](<https://devfeed.tech/topics/developer-tools.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [toolchain](<https://devfeed.tech/topics/toolchain.md>), [builds](<https://devfeed.tech/topics/builds.md>), [macOS](<https://devfeed.tech/topics/macos.md>), [Tutorial](<https://devfeed.tech/topics/tutorial.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [binaries](<https://devfeed.tech/tags/binaries.md>), [build](<https://devfeed.tech/tags/build.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [debug](<https://devfeed.tech/tags/debug.md>), [debuggers](<https://devfeed.tech/tags/debuggers.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [elf](<https://devfeed.tech/tags/elf.md>), [info](<https://devfeed.tech/tags/info.md>), [ios](<https://devfeed.tech/tags/ios.md>), [lldb](<https://devfeed.tech/tags/lldb.md>), [macos](<https://devfeed.tech/tags/macos.md>), [metadata](<https://devfeed.tech/tags/metadata.md>)

### AI overview

Apple Mach-O binaries typically keep debug info in intermediate object files and store references to them, so LLDB needs the referenced objects and source files to be available. The text explains how Bazel builds can lose debugging details when paths point into temporary sandboxes, remote caching omits object files, the wrong C++ toolchain is selected, or debug info is disabled or stripped. It describes using `-oso_prefix` and Clang path remapping flags for stable paths, downloading intermediates and ensuring the `apple_support` toolchain is selected, and using dSYM bundles to collect dependency debug info so intermediates can later be removed. dSYMs take time to produce and must be created during Bazel linking with the needed intermediates; absolute source paths can still require remapping. It also covers source maps for prebuilt artifacts and notes that shared libraries need their own valid object references or dSYMs.

### Source excerpt

Apple platforms (macOS, iOS, etc), and specifically Mach-O binaries, have a slightly different approach to debug info than ELF binaries for Linux. If you are familiar with Xcode, you might have seen a few related settings that control what is produced and wondered what the trade-offs are. The goal of this post is to help you debug cases where these differences lead to a degraded debugging experience in lldb so that you can fix them. If you have a particularly complex build, potentially managed by Bazel1 or another tool, especially if you are using distributed builds, you are even more likely to hit issues. Let's dive in to how the pieces fit together. A brief explanation of debug info Debug info is metadata produced by the compiler that is consumed by debuggers (like lldb), profilers, and other tools. It is used to map runtime information, like addresses, function arguments, and stack traces, back to the source that was used to produce the binary. Without this information debugging in lldb shows primarily raw instructions and addresses, which is rarely acceptable for common debugging workflows. Inspecting debug info When building for Apple platforms debug info isn't contained in the final binary (this is the primary difference from the default Linux workflows). Instead the binary contains references to the files where lldb can find it (this is conceptually similar to if you use -gsplit-dwarf on Linux). Let's inspect some binaries to see what this really means. First we create a small binary: $ cat main.c int main() { return 0; } $ clang main.c -g -c -o main.o $ clang main.o -o main If we attempt to inspect the debug info contained in main, we find nothing: $ dwarfdump main # use llvm-dwarfdump if not on macOS main: file format Mach-O arm64 .debug_info contents: However when we debug this binary in lldb, you will correctly see the source file and line number information: $ lldb -- main (lldb) target create "main" Current executable set to '/tmp/demo/main' (arm64). (l

## Enhancing Security Metadata in BCR with Attestation Support

DevFeed: [Enhancing Security Metadata in BCR with Attestation Support](<https://devfeed.tech/articles/enhancing-security-metadata-in-bcr-with-attestation-support-53172.md>)

Original publisher: [Read original article](<https://blog.bazel.build/2025/08/01/enhancing-security-metadata-in-bcr.html>)

Published: 2025-08-01T00:00:00Z

Content type: release

Language: en

Sources: [Bazel Blog](<https://devfeed.tech/sources/bazel-blog.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>), [open-source-security](<https://devfeed.tech/topics/open-source-security.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [releases](<https://devfeed.tech/topics/releases.md>)

Tags: [attestation](<https://devfeed.tech/tags/attestation.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [releases](<https://devfeed.tech/tags/releases.md>), [security](<https://devfeed.tech/tags/security.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>)

### AI overview

Bazel Central Registry has added attestation support for Bazel modules, enabling maintainers to publish signed provenance and consumers to access more security metadata when evaluating dependencies. The update includes revised GitHub Actions workflows, pre-submit verification, and registry support for preserving and displaying attestations.

### Source excerpt

Bazel Central Registry is the go-to source for discovering and managing Bazel modules. Over the last few months Aspect Build, Bazel Central Registry and the Google Open Source Security Team have been working together on enhancing the security of the software supply chain. We are happy to announce that attestation support in BCR is now available. This includes updated GitHub Actions for packaging and releasing rulesets. It also enables pre-submit verification of this new security metadata on the registry. For module maintainers this allows easy publishing of signed provenance with module releases. For consumers, this means a greater availability of security metadata to make informed decisions when including or updating dependencies. Get Started Today Publishing Attestations If you are using release_ruleset with the publish-to-bcr legacy app to publish your modules to BCR, you should: upgrade your release_ruleset to use the new attestation generating workflow follow the instructions to setup the new publish-to-bcr workflow To see how this affects a release, let's use the example of aspect_rules_lint which has been publishing modules with attestations since v1.3.4. You will see a new publishing artifact `attestations.json' that contains information about your attestations. On successful publication, BCR will preserve and mirror attestations for publishing artifacts. Please note that since BCR does not mirror the source archive, it also does not mirror the source archive's attestation. The BCR UI will attach a blue indicator to a release version informing users that attestations are available for consumption. Verifying Attestations Once you've generated and published your attestations, you can validate them. For the purposes of this example, we will once again use aspect_rules_lint. There are three critical files to attest to cover a module version: MODULE.bazel (published to BCR) source.json (published to BCR) the packaged module source (not hosted on BCR): rules_lint-

## Integration of AppIntents to a Project that uses Bazel Build System

DevFeed: [Integration of AppIntents to a Project that uses Bazel Build System](<https://devfeed.tech/articles/integration-of-appintents-to-a-project-that-uses-bazel-build-system-56759.md>)

Original publisher: [Read original article](<https://engineering.mercari.com/en/blog/entry/20250625-integration-of-appintents-to-a-project-that-uses-bazel-build-system/>)

Author: Cyan

Published: 2025-06-27T07:00:50Z

Content type: tutorial

Language: en

Sources: [Mercari Engineering](<https://devfeed.tech/sources/mercari-engineering.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [implementation](<https://devfeed.tech/topics/implementation.md>), [Framework](<https://devfeed.tech/topics/framework.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [guide](<https://devfeed.tech/tags/guide.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [ios](<https://devfeed.tech/tags/ios.md>)

### AI overview

An iOS team describes integrating Apple's AppIntents framework into a project that uses Bazel. The article covers the implementation approach, BUILD-file configuration, and a comparison with the older Intents framework.

### Source excerpt

Hey guys, it's Cyan from the Mercoin iOS Team. This time, I would like to write about my experience integrating the new AppIntents framework to an iOS project that uses a Bazel build system. Followed by the actual implementation guide as well as a brief comparison of the new AppIntents vs the old Intents frameworks. [...]

## Automating code deletion with Gemini (and a little Python)

DevFeed: [Automating code deletion with Gemini (and a little Python)](<https://devfeed.tech/articles/automating-code-deletion-with-gemini-and-a-little-python-31143.md>)

Original publisher: [Read original article](<https://technicalwriting.dev/2025/04/gn/index.html>)

Published: 2025-04-29T00:00:00Z

Content type: tutorial

Language: en

Sources: [Technicalwriting](<https://devfeed.tech/sources/technicalwriting-dev.md>)

Topics: [Google AI](<https://devfeed.tech/topics/google-ai.md>), [Python](<https://devfeed.tech/topics/python.md>), [API](<https://devfeed.tech/topics/api.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Code](<https://devfeed.tech/topics/code.md>), [bazel](<https://devfeed.tech/topics/bazel.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [automation](<https://devfeed.tech/tags/automation.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [build](<https://devfeed.tech/tags/build.md>), [code](<https://devfeed.tech/tags/code.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [genai](<https://devfeed.tech/tags/genai.md>), [gn](<https://devfeed.tech/tags/gn.md>), [python](<https://devfeed.tech/tags/python.md>), [script](<https://devfeed.tech/tags/script.md>)

### AI overview

The article describes a hybrid automation workflow that uses Python for repository-wide file discovery and filtering, then uses the Gemini API to remove documentation-generation features from 235 GN build files after a migration to Bazel.

### Source excerpt

Removing code from over 200 GN build files with Python and the Gemini API.

## Automating code deletion with Gemini (and a little Python)

DevFeed: [Automating code deletion with Gemini (and a little Python)](<https://devfeed.tech/articles/automating-code-deletion-with-gemini-and-a-little-python-55454.md>)

Original publisher: [Read original article](<https://technicalwriting.dev/blog/2025/04/gn/index.html>)

Published: 2025-04-29T00:00:00Z

Content type: tutorial

Language: en

Sources: [Technicalwriting](<https://devfeed.tech/sources/technicalwriting-dev.md>)

Topics: [Code](<https://devfeed.tech/topics/code.md>), [Google AI](<https://devfeed.tech/topics/google-ai.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Python](<https://devfeed.tech/topics/python.md>), [API](<https://devfeed.tech/topics/api.md>), [Generative AI](<https://devfeed.tech/topics/generative-ai.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [builds](<https://devfeed.tech/topics/builds.md>), [bazel](<https://devfeed.tech/topics/bazel.md>), [Script](<https://devfeed.tech/topics/script.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [automation](<https://devfeed.tech/tags/automation.md>), [bazel](<https://devfeed.tech/tags/bazel.md>), [build](<https://devfeed.tech/tags/build.md>), [builds](<https://devfeed.tech/tags/builds.md>), [code](<https://devfeed.tech/tags/code.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [genai](<https://devfeed.tech/tags/genai.md>), [gn](<https://devfeed.tech/tags/gn.md>), [python](<https://devfeed.tech/tags/python.md>), [repository](<https://devfeed.tech/tags/repository.md>), [script](<https://devfeed.tech/tags/script.md>), [source-code](<https://devfeed.tech/tags/source-code.md>)

### AI overview

The article describes using Gemini 2.0 Flash and Python to remove obsolete docgen features from more than 200 GN build files after a migration to Bazel. It presents a hybrid workflow that combines conventional scripting for file discovery and filtering with Gemini for file-by-file code modifications.

### Source excerpt

Removing code from over 200 GN build files with Python and the Gemini API.

## Sphinx + Bazel: the good, the bad, and the ugly

DevFeed: [Sphinx + Bazel: the good, the bad, and the ugly](<https://devfeed.tech/articles/sphinx-bazel-the-good-the-bad-and-the-ugly-55452.md>)

Original publisher: [Read original article](<https://technicalwriting.dev/blog/2025/03/context/index.html>)

Published: 2025-03-25T00:00:00Z

Content type: article

Language: en

Sources: [Technicalwriting](<https://devfeed.tech/sources/technicalwriting-dev.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [cli](<https://devfeed.tech/tags/cli.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [sphinx](<https://devfeed.tech/tags/sphinx.md>)

### AI overview

An experienced technical writer evaluates using Bazel to manage Sphinx documentation projects, drawing on a migration of a large site with multiple API reference generation pipelines. The article discusses when Bazel may improve maintenance, environment setup, and project workflows compared with custom shell scripts.

### Source excerpt

Strengths and weaknesses of orchestrating Sphinx projects with Bazel.

## Sphinx + Bazel: the good, the bad, and the ugly

DevFeed: [Sphinx + Bazel: the good, the bad, and the ugly](<https://devfeed.tech/articles/sphinx-bazel-the-good-the-bad-and-the-ugly-31141.md>)

Original publisher: [Read original article](<https://technicalwriting.dev/2025/03/context/index.html>)

Published: 2025-03-25T00:00:00Z

Content type: opinion

Language: en

Sources: [Technicalwriting](<https://devfeed.tech/sources/technicalwriting-dev.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [software-development](<https://devfeed.tech/topics/software-development.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [shell-script](<https://devfeed.tech/tags/shell-script.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [sphinx](<https://devfeed.tech/tags/sphinx.md>)

### AI overview

An experienced technical writer discusses the strengths and weaknesses of managing Sphinx documentation projects with Bazel. The article explains how Bazel can orchestrate Sphinx workflows and describes reported maintenance and development-environment benefits, while helping readers decide whether it fits their project.

### Source excerpt

Strengths and weaknesses of orchestrating Sphinx projects with Bazel.

## Orchestrate Sphinx projects with Bazel

DevFeed: [Orchestrate Sphinx projects with Bazel](<https://devfeed.tech/articles/orchestrate-sphinx-projects-with-bazel-55453.md>)

Original publisher: [Read original article](<https://technicalwriting.dev/blog/2025/03/tutorial/index.html>)

Published: 2025-03-25T00:00:00Z

Content type: tutorial

Language: en

Sources: [Technicalwriting](<https://devfeed.tech/sources/technicalwriting-dev.md>)

Topics: [bazel](<https://devfeed.tech/topics/bazel.md>), [Tutorial](<https://devfeed.tech/topics/tutorial.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>), [builds](<https://devfeed.tech/topics/builds.md>), [Code](<https://devfeed.tech/topics/code.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [GitHub Pages](<https://devfeed.tech/topics/github-pages.md>), [Shell](<https://devfeed.tech/topics/shell.md>)

Tags: [bazel](<https://devfeed.tech/tags/bazel.md>), [build](<https://devfeed.tech/tags/build.md>), [build-system](<https://devfeed.tech/tags/build-system.md>), [code](<https://devfeed.tech/tags/code.md>), [commands](<https://devfeed.tech/tags/commands.md>), [configure](<https://devfeed.tech/tags/configure.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [github](<https://devfeed.tech/tags/github.md>), [github-pages](<https://devfeed.tech/tags/github-pages.md>), [learn](<https://devfeed.tech/tags/learn.md>), [linux](<https://devfeed.tech/tags/linux.md>), [macos](<https://devfeed.tech/tags/macos.md>), [shell](<https://devfeed.tech/tags/shell.md>), [sphinx](<https://devfeed.tech/tags/sphinx.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

An end-to-end tutorial for managing Sphinx documentation projects with Bazel. It covers setting up the build system, building and inspecting documentation, previewing it locally, adding extensions, and deploying to GitHub Pages.

### Source excerpt

An end-to-end tutorial on managing a Sphinx project with Bazel.

[Next page](<https://devfeed.tech/topics/bazel.md?cursor=WyIyMDI1LTAzLTI1VDAwOjAwOjAwKzAwOjAwIiwgImIzMjBmNDg0LWFiMDktNDRiNC04ZmRkLTkyYjJmZDFkZTk0MCJd>)