Windows worker about bb-remote-execution HOT 6 CLOSED

Just adding my +1 for a Windows worker/runner. Scheduler, storage etc. is planned to run on Linux, so in my case I don't need that working on Windows (also working on getting a Linux system working, then will try Mac)

from bb-remote-execution.

Hi Marka,

Getting Buildbarn to work on Windows is something that I haven't experimented with. I think it would be better to first start out getting bb-storage to build and work on Windows, as the other bb-* repositories depend on it. Doing the build on Windows itself is something that will likely break, but you can just run the following on Linux/macOS:

bazel build --platforms=@io_bazel_rules_go//go/toolchain:windows_amd64 //cmd/bb_storage

The build currently breaks, because this specific source file has absolutely not been written with Windows in mind:

https://github.com/buildbarn/bb-storage/blob/master/pkg/filesystem/local_directory.go

We should likely rename it to local_directory_unix.go and provide a separate implementation for Windows. Is this something you'd be interested in working on?

from bb-remote-execution.

Hi,

Thanks for your quick reply.

My idea is to build a cluster to build Linux/Windows code (because of c++). Your current approach packages everything into docker images (which is a great idea, it simplifies the basic setup). In the end I want to have a machine providing a remote cache and different workers for remote execution to build Linux/Windows. (means bb_storage always runs on a Linux machine while workers run on Windows/Linux and connect to the same storage). If this is possible I am interested in, at least running runner/worker/scheduler on a windows machine.

from bb-remote-execution.

Hi there,

Yes, I understood that part; you only want to run bb-worker + bb-runner on Windows. But here's the issue: bb-worker depends on bb-storage in terms of code. bb-worker uses the same storage layer as bb-storage under the hood. This means that if bb-storage doesn't build on Windows, bb-worker won't build either.

from bb-remote-execution.

Once the storage is factored to work on Windows, there remains the problem of a worker that works on Windows (I believe); if we address #2 with the new worker protocol then we might be able to have some interop between BuildBarn and the workers we are working on for BuildGrid.

from bb-remote-execution.

Closing this issue due to inactivity. I’m not against adding support for Windows. PRs are more than welcome! It’s just that issues that stay open for a year without meaningful progress are distracting. :-)

from bb-remote-execution.