ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #bazel
Bazel utilizes a content-addressable storage (CAS) system to ensure that action outputs are retrieved based on a hash of their inputs. In a remote caching environment, achieving consistent cache hits across different CI runners and developer workstations is critical for build performance. There is a design uncertainty regarding how Bazel handles absolute pat
Goal Understand why Bazel emits the error “error: no such package” for a target that appears to have a correct BUILD file, focusing on the analysis phase and how the message varies across Bazel versions. Constraints and uncertainty In Bazel 5.x the error includes the missing package path, whereas Bazel 4.x may omit the path unless the build is run with --ver
Context Bazel 7.0 lowered the default --max_idle_secs from 10800 to 1800 seconds, aiming to reduce idle memory and CPU consumption in sporadic CI or developer environments. This change accelerates server shutdown, which lowers baseline resource costs but increases cold-start latency for the next build because the analysis cache and persistent workers are tor