Florian Weikert

We stopped supporting Ubuntu 14.04 binaries in June 2019: https://github.com/bazelbuild/bazel/commit/b6d78a5d0e9038fdf21732f6c6b98fc8379e7eb2 I wonder why this happens on 18.04, though.

https://github.com/bazelbuild/bazelisk/releases/tag/v1.12.1 contains the fix

The real fix would be https://github.com/bazelbuild/continuous-integration/issues/1402

I don't have an M1 machine to test, but shouldn't line 35 handle this problem? It's also possible that DarwinFallback() cannot handle commits (just a theory).

Filed https://github.com/buildkite/agent/issues/1303

Nice, thank you! I triggered a rerun of the failing Windows test.

I'd be happy if someone could dogfood my instructions on how to update Bazelisk: https://github.com/bazelbuild/continuous-integration/pull/574/files#diff-62d13c1279fbb93b58652272e3c24c08R54 Lack of permissions is something that could happen (and that we should fix).

EngProd already has plans to add release capabilities to Bazel CI in Q3, especially motivated by Bazelisk, Buildtools and Bazel itself. We're happy to address your use cases, too :)

cc @philwo

There's `bazel help flags-as-proto` if you don't want to parse unstructured text. The default flag values have to be added to https://github.com/bazelbuild/bazel/blob/master/src/main/protobuf/bazel_flags.proto, but that' trivial.