Philipp Wollermann comments

Results 160 comments of


                                            Philipp Wollermann

Bazelisk broken with Bazel@Head on Windows

I'm pretty sure we didn't touch our Windows images in a long time :/ @meteorcloudy Any idea?

Bazelisk broken with Bazel@Head on Windows

The job magically turned green again on the third try: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1915#9e108f5e-8798-445c-9732-2685e48c0efc 😅

update build_bazel_rules_nodejs and update bazel version in tests so …

Thank you!

update build_bazel_rules_nodejs and update bazel version in tests so …

I can test this PR on my M1 machine and merge it, when my https://github.com/bazelbuild/bazelisk/pull/343 has been merged.

USE_BAZEL_VERSION with absolute path results in "invalid version unknown"

Hi @keith, Yes, that’s exactly the problem. Bazelisk currently cannot extract the version number from a given local Bazel binary, which is why it can’t fetch the flags needed to...

USE_BAZEL_VERSION with absolute path results in "invalid version unknown"

Yeah, we could do that. I guess the format is stable enough that it shouldn’t cause issues.

USE_BAZEL_VERSION with absolute path results in "invalid version unknown"

I recently found out that we have support for `bazel --version`, which does not require starting up a Bazel server or extracting the install_base, so it's very fast. We could...

bazel-at-head-plus-downstream needs to be split and/or individual projects need to be able to add flags

@fweikert Can you have a look? You’re the expert on this stuff :)

Publish build output via Buildkite (and GCS)

@fweikert What do you mean with "build output"? The build log? Or the entire bazel-out folder?

rules_go fails with bazel@HEAD, but not tied to a commit

@c-parsons I think this is caused by the release of Bazel 0.27.0. We didn't change anything on CI itself in quite a while.