/explore
|
You are here 
|
blog.bazel.build | ||
| | | | |
jmmv.dev
Today marks the 10th anniversary of Bazel's public announcement so this is the perfect moment to reflect on what the next generation of build systems in the Bazel ecosystem may look like. I write this with the inspiration that comes from attending the first ever conference on Buildbarn, one of the many remote execution systems for Bazel. In the conference, Ed Schouten, the creator of Buildbarn, presented Bonanza: a skunkworks reimagination of Bazel for truly large builds. |
|
| | | | | ||
| | | | |
bazel.build
[AI summary] This article explains the concept of hermeticity in Bazel builds, detailing its benefits for reproducibility and optimization while providing strategies to identify and fix non-hermetic behaviors. |
|
| | | | | ||
| | | | |
fzakaria.com
Bazel is a pretty amazing tool but it's definitely full of it's warts, sharp edges and arcane knowledge. The appeal to most who adopt Bazel is the ability to memoize much of the build graph if nothing has changed. Furthermore, while leveraging remote caches, build results can be shared across machines making memoization even more effective. This was a pretty compelling reason to adopt Bazel but pretty soon many noticed, especially on their CI systems, lots of unecessary data transfers for larger codebases. If the network is poor, the benefits of remote caching (memoization) can be outweighed by the cost to download the artifacts. |
|
| | | | | ||
| | | | |
moscardino.net
A look at React Native and Ionic Framework. |
|
| | | |||
