support for bazel build on network workspaces

[Shubham Srivastava]

Does bazel support building from workspaces present in network drives on Windows?

I ask this as I have been unable to get it working and just wanted to check in this community if someone has been able to do this and it is a supported workflow.

Best,

Shubham

[Filip Filmar]

Could you describe the specific issues you were facing in more detail? What did you try, what did you want to get out of it, what happened, what did you expect should have happened, etc.

I think that you want to introduce any sort of network latency in your build process with utmost care, and should determine whether you're making the right tradeoff.

F
 

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bazel-discuss/3c228935-110f-4379-a6c9-a51a2af8bbd1n%40googlegroups.com.

[Shubham Srivastava]

I am running into the problem that I have also described in  Help needed in getting bazel build command working on Windows from a mapped network drive · Issue #28321 · bazelbuild/bazel 

Does it help clarify my setup?

-Shubham  

[Filip Filmar]

On Thu, Jan 22, 2026 at 6:14 AM Shubham Srivastava <srivshu...@gmail.com> wrote:

I am running into the problem that I have also described in  Help needed in getting bazel build command working on Windows from a mapped network drive · Issue #28321 · bazelbuild/bazel 

Does it help clarify my setup?

Frankly, I'm a bit confused now. You claim in your other message that your install base is on a local disk. But the link you provided seems to imply that there seem to be issues renaming a file in place in a path on the `C:\` drive, which is something that could happen on a network drive. It's been a while since I was last using Windows, but I think that `C:\` is usually local disk. In that case it might be an issue with your local disk, not your networked setup.

I expect that with bazel, if you keep your read-only files on a reasonably reliable network drive and use a local cache directory, you should only incur network latency for reads.

That said, in many realistic situations, network drives aren't the answer for development. In my area, local storage is cheap enough that if I fill up my 4T SSD, I can buy an 8TB SSD without hesitation. So, maybe, ensuring you have enough local storage might be a better use of your time, as it would side-step any networking issues you might have encountered.

In short, to me it seems like you are describing an obstacle encountered while pursuing an unstated goal. I suggest you re-assess how you can reach your goal differently, whatever that goal may be.

F