Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Bazel setup action change #519

Merged
merged 1 commit into from
Feb 6, 2024
Merged

Conversation

snazy
Copy link
Member

@snazy snazy commented Feb 1, 2024

Force bazelisk to use bazel 6.5.0, because latest 7.0.2 does not work

dimas-b
dimas-b previously approved these changes Feb 1, 2024
@snazy snazy force-pushed the setup-bazel branch 3 times, most recently from f4384a7 to 146cbbe Compare February 5, 2024 17:56
Force bazelisk to use bazel 6.5.0, because latest 7.0.2 does not work
@@ -94,12 +94,6 @@ jobs:
key: bazel-${{ hashFiles('**/.gitmodules') }}
restore-keys: bazel-

- name: Setup bazel
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bazelisk is now included in the github-runner image.
Just need to make sure that we're using a Bazel version that works with the conformance tests.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: looks like bazel introduced a behavioral change in v7, that lets the conformance tests build fail.

@snazy snazy merged commit f075f9a into projectnessie:main Feb 6, 2024
4 checks passed
@snazy snazy deleted the setup-bazel branch February 6, 2024 17:46
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