I Went to BazelCon 2025 – Here’s Everything You Need to Know
#Clang #CLion #Events #News #Bazel #Buildtools
At #BazelCon, Malte Poll presented asset-fuse, a FUSE-based filesystem for bringing large files into Bazel or Buck2. 🗂️
Watch the recording: https://www.youtube.com/watch?v=i07kTWg38q8
Want to learn the Bazel basics — including tips for debugging build errors?
▶️ Watch the recording of Alejandro Gómez Londoño’s #BazelCon training: https://www.youtube.com/watch?v=1CX6x2siC28
🌘 遷移至 Bazel 符號宏
➤ 從傳統到符號:掌握 Bazel 宏的現代化遷移之路
✤ https://www.tweag.io/blog/2025-11-20-migrating-bazel-symbolic-macros/
本文為資深 Bazel 工程師或負責現代化程式碼建構的中層技術人員提供指南,闡述如何從傳統宏遷移至 Bazel 的符號宏。符號宏透過強化類型參數、限定目標可見性,提升了程式碼的清晰度與管理性。文中探討了符號宏在命名約束、存取權限、參數傳遞與預設值設定上的具體實踐與注意事項,並透過程式碼範例說明如何正確運用這些特性,以實現更穩健、易於理解的建構系統。
+ 這篇文章對符號宏的解釋相當深入,特別是關於命名規則的部分,非常實用!
+ 感謝作者詳細的比較,讓我更清楚傳統宏和符號宏在參數處理上的差異,避免了不少潛在 bug。
#Bazel #軟體建構 #開源
At #BazelCon, Malte Poll presented rules_img, a faster and more efficient approach to building container images with Bazel. 🛠️
Watch the full recording: https://www.youtube.com/watch?v=biYXmAv4Ppk
Think Bazel is just for code? Think again.
🎬 Watch the recording of Daniel Thagard’s #BazelCon talk to learn how to connect build systems with media editing workflows: https://www.youtube.com/watch?v=YrcsDu63OWA
New blog post from Alexey Tereshenkov. For you experience #Bazel engineers migrating from legacy macros to symbolic macros as introduced in Bazel 8. Read for Alex's guide with hands-on examples, actionable tips, and subtleties to be wary of: https://www.tweag.io/blog/2025-11-20-migrating-bazel-symbolic-macros/
Didn't make it to #BazelCon?
Watch Guillaume Maudoux’s talk on Python dependency management with FawltyDeps in Bazel. 🐍
🎥 Check out the recording: https://www.youtube.com/watch?v=5j2bb44CV1g
Zatrudniamy w SoftwareMill! Praca w pełni zdalna, #Kotlin, #Scala, #Rust na backendzie; #DevOps, czyli kubernetesy w chmurze. Oferty z widełkami: https://softwaremill.com/join-us/
SoftwareMill jest częścią grupy VirtusLab Group, gdzie szukamy: #Golang, #Scala na backendzie; #Bazel dla miłośników przyspieszania buildów; #Python +ML/LLM; #DevOps + #Spinnaker; i na deser #IDE oraz #IntelliJ engineer. Więcej (z widełkami): https://careers.virtuslab.com
Niejedna / niejeden znajdzie tu coś dla siebie :) Zapraszamy!
We loved connecting at #BazelCon last week as a Silver Sponsor! 🥈
Missed our VP Andreas Herrmann’s talk?
He covers how Buck2 builds Haskell, how it compares to Bazel, and what it means for efficiency.
🎥 Watch the full talk: https://www.youtube.com/watch?v=eA-3Gfr4epU
I’m looking for someone to join me at Fractile working on #DevEx, but with a twist…
Sure, you’ll be doing all the normal #DeveloperExperience things, like working on #Bazel rules, tweaking #CI, optimising the #monorepo configuration, etc., etc., etc., but you’ll also get the chance to shape the Developer Experience for our customers, and make the #AI accelerators we’re developing easy and pleasant to work with.
Interested? Here’s the link to apply…
https://job-boards.eu.greenhouse.io/fractile/jobs/4562362101
Nice:
“Build System Trade-Offs”, Jynn Nelson (https://jyn.dev/build-system-tradeoffs).
Via HN: https://news.ycombinator.com/item?id=45790874
On Lobsters: https://lobste.rs/s/uwyfpy/build_system_tradeoffs
#Build #Programming #BuildSystems #Cargo #Make #Bazel #Ninja
I wrote a piece for the Slack Engineering Blog about how #Bazel combined with software engineering principles to accelerate builds from 60 minutes to under 10 minutes, and achieve #ContinuousDelivery.
https://slack.engineering/build-better-software-to-build-software-better/
There is now a FOSS version of my Okapi ray tracer - you can clone it from https://github.com/Vertexwahn/OkapiRT. It uses Bazel as build system. Was inspired Pbrt, Nori, Mitsuba, Luisa Compute #bazel #raytracing #3d #cpp #pbrt
We're proud sponsors of BazelCon 2025! 🎉
Atlanta on Nov 10-11 - we can't wait to connect with the Bazel community!
At Trunk, we've built our CI Reliability Platform specifically for teams running Bazel in massive monorepos. Companies like Brex, Waabi, Applied Intuition, and Glydways trust us to keep their builds fast and reliable with target-parallel merge queues, BEP-native flaky test detection, and cache-aware intelligence.
Stareți de pe Athos le cere grecilor să nu ia cărțile de identitate digitale noi - identitatea digitală "Trăim, fără îndoială, în vremuri apocaliptice. Deci, să dobândim o "îngrijorare bună" cu privire la ceea ce se întâmplă în jurul nostru. În spatele comodităților promise ale societății digitale moderne se află cătușele unui sistem neliberal", au subliniat călugării. 👉 https://c.aparatorul.md/kvzc9 👈 #Antihrist #anulareanumerarului #Apocalipsei #Atoniții #bazel...
https://c.aparatorul.md/kvzc9
💻🤔 "Trusting builds with #Bazel #remote execution" 🤯🤯 A riveting saga about making Bazel builds less dodgy by adding #remote #execution to the mix. Because apparently, the thrill of relying on a temperamental remote #cache just wasn't enough! 🙄🔧
https://jmmv.dev/2025/09/bazel-remote-execution.html #Trust #Issues #Software #Development #Tech #News #HackerNews #ngated
Trusting builds with Bazel remote execution
https://jmmv.dev/2025/09/bazel-remote-execution.html
#HackerNews #Trusting #builds #Bazel #remote #execution #softwaredevelopment #devops #cloudcomputing #continuousintegration
🌘 你可能誤解了 BUILD 檔案的用法
➤ 重新認識 BUILD 檔案:架構定義與依賴約束的關鍵
✤ https://blogsystem5.substack.com/p/you-are-holding-build-files-wrong
本文作者 Julio Merino 指出,許多人誤以為 Bazel 的 BUILD 檔案僅是用來重複宣告程式碼中的依賴關係,因而認為其是多餘的。然而,作者強調 BUILD 檔案的真正價值在於它能以程式化方式定義軟體的高階架構,並將模組間的依賴關係獨立於程式碼之外。透過「精簡」的 BUILD 檔案,定義代表概念的目標,並善用可見性規則(visibility rules),可以有效防止不當的跨模組依賴,確保軟體架構的清晰與維護性。即使編譯效能受影響,也可視為模組化問題的徵兆,應予以修正。
+ 這篇文章讓我對 BUILD 檔案的理解改觀!原來它不只是重複宣告,而是架構的關鍵。
+ 作者提到了可見性規則,這對於管理複雜專案的依賴關係非常重要,感謝分享。
#軟體架構 #Bazel #BUILD 檔案 #依賴管理
Oh, and don't forget that #Google donated $1,000,000 last year with a more narrow target: Rust and C++ interoperability: https://rustfoundation.org/media/google-contributes-1m-to-rust-foundation-to-support-c-rust-interop-initiative/.
When I was at Google, I had a lot of fun writing #Rust and calling into it from #Cpp with #Crubit. It supports bi-directional interop between the two languages, for some subset of both. See https://github.com/google/crubit if you're interested, though I don't actually know if this builds in the open without using #Bazel.