Skip to content

Use Bazelisk instead of Bazel in GitHub Actions.#504

Draft
PiotrSikora wants to merge 2 commits intoproxy-wasm:mainfrom
PiotrSikora:bazelisk
Draft

Use Bazelisk instead of Bazel in GitHub Actions.#504
PiotrSikora wants to merge 2 commits intoproxy-wasm:mainfrom
PiotrSikora:bazelisk

Conversation

@PiotrSikora
Copy link
Copy Markdown
Member

bazel-contrib/setup-bazel installs only "bazelisk" binary, not "bazel".

The existing jobs worked on hosted GitHub runners, since both binaries
are preinstalled, but "bazel" is not available when testing locally.

bazel-contrib/setup-bazel installs only "bazelisk" binary, not "bazel".

The existing jobs worked on hosted GitHub runners, since both binaries
are preinstalled, but "bazel" is not available when testing locally.

Signed-off-by: Piotr Sikora <code@piotrsikora.dev>
@PiotrSikora
Copy link
Copy Markdown
Member Author

This is blocked on #492 (s390x), since its Docker image doesn't have bazelisk binary (and even if it did, then there are no official Bazel releases for s390x anyway...).

@PiotrSikora PiotrSikora marked this pull request as draft March 6, 2026 08:52
@leonm1
Copy link
Copy Markdown
Contributor

leonm1 commented Apr 6, 2026

Any argument against closing this PR? It will be forever blocked since we have decided to continue using s390x in CI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants