News for hackers. Stuff that matters.
Re:A faster path to container images in Bazel by dilyevsky on Wednesday December 24, 2025 @03:36PM (#46378986)
Making heavy use of mostly remote caches and execution was one of the original design goals of Blaze (Google's internal version) iirc in an effort to reduce build time first and foremost. So kind of the opposite of what you're suggesting. That said, fully air-gapped builds can still be achieved if you just host all those cache blobs locally.
Re:A faster path to container images in Bazel by forrestthewoods on Wednesday December 24, 2025 @04:02PM (#46379184)
> So kind of the opposite of what you're suggesting.

I don’t think they’re opposites. It seems orthogonal to me.

If you have a bunch of remote execution workers then ideally they sit idle on a full (shallow) clone of the repo. There should be no reason to reset between jobs. And definitely no reason to constantly refetch content.