PR #650: Fix CI: Use fixed Bazel version

Bazel in CI automatically updates itself to the latest release. Version 4.0 released yesterday breaks builds. This patch forces CI to run requested Bazel version (3.7). GitHub PR #650 Copybara import of the project: - f4600a8 CI: Use fixed Bazel version by Mariusz Glebocki <[email protected]> - 9f26b7d Merge f4600a8 into 2af11... by Mariusz Glebocki <[email protected]> Closes #650 PiperOrigin-RevId: 353664997
chipsalliance · Jan 26, 2021 · bc392aa · bc392aa
1 parent 2af116e
commit bc392aa
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/.github/settings.sh b/.github/settings.sh
@@ -27,6 +27,9 @@ fi
 export GIT_VERSION=${GIT_VERSION:-$(git describe --match=v*)}
 
 export BAZEL_VERSION=3.7.0
+# Without following environment variable set, Bazel updates itself to the
+# latest version
+export USE_BAZEL_VERSION=$BAZEL_VERSION
 
 # TODO(b/171679296): re-enable c++11 support
 #   by downgrading kythe build requirements.