infra: Fix bazel 8.0 WORKSPACE disable problem #12838
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The base-builder depends on the google/fuzztest project to precompile the centipede module. The google/fuzztest uses the WORKSPACE approach to provide repository location. But since bazel 8 (released yesterday), the WORKSPACE approach is no longer enabled by default (https://bazel.build/versions/8.0.0/external/migration). Also, in the Dockerfile of the base-builder, we automatically install the latest version of bazel (which is bazel 8 from yesterday), that make the building of fuzztest and eventually the base-builder failed.
This PR fixes the problem temporary by forcing the installation of bazel version 7.4.0 to avoid the disabling of WORKSPACE defintion, this make the build of google/fuzztest success.