Explore >> Select a destination
|
You are here 
|
blog.bazel.build | ||
| | | | |
bazel.build
|
|
| | | | | ||
| | | | |
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. | |
| | | | |
enoent.fr
|
|
| | | | | Random musings of a software engineer. | |
| | | | |
g-w1.github.io
|
|
| | | See part 2 for this post here | ||
