Call to action: Windows quality drive across bazel ecosystem

[peakschris]

Bazel adoption for those of us who must support windows has been pretty frustrating over the last few years with some key bazel rulesets failing with gaps or bugs. Several of us have been working specifically on improving windows test coverage and fixing issues across the bazel ecosystem.

I have been working on fixing windows gaps and enabling CI by default in bazel-lib and rules_oci.

Other folks active in windows quality area:

• @alexeagle supporting windows testing, windows binaries & fixes across aspect ecosystem & other rules
• @fmeum windows improvements related to bazel coverage [WIP] and in rules

This is a call to action; if you are a ruleset maintainer maybe you already have got good Windows testing - please note so below; if not please consider enabling windows testing in your CI matrixes. And please note your existing successes on this thread.

Note: By default I would suggest we test Windows with:

• symlinks enabled [--windows_enable_symlinks]
• runfiles disabled [this is the bazel default] (and optionally runfiles enabled too)

[malkia]

I've been using bazel almost exclusively on Windows, and I'm glad this issue was raised. Thank you!

One small hint that keeps poppin in different rulesets: if your rules use cd <dir>, please switch to cd /D <dir> (alternatively pushd - but it's not clean).