build: fix @bazel/bazel to bazelisk leftovers (#36132)
A few leftovers from from `@bazel/bazel` to `@bazel/bazelisk` migration are still there. This commit fixes those, so that the repository no longer relies on `@bazel/bazel`. PR Close #36132
This commit is contained in:

committed by
Andrew Kushnir

parent
e342ffd855
commit
fb92f5de1a
@ -7,8 +7,8 @@ set -u -e -o pipefail
|
||||
# Publish them to npm (tagged next)
|
||||
|
||||
# We need to resolve the Bazel binary in the node modules because running Bazel
|
||||
# through `yarn bazel` causes additional output that throws off the command stdout.
|
||||
BAZEL_BIN=$(yarn bin)/bazel
|
||||
# through `yarn bazelisk` causes additional output that throws off the command stdout.
|
||||
BAZEL_BIN=$(yarn bin)/bazelisk
|
||||
# Build into a distinct output location so that artifacts from previous builds are not reused
|
||||
BAZEL_OUTPUT_BASE=$(mktemp -d -t angular-release-latest.XXXXXXX)
|
||||
BAZEL="$BAZEL_BIN --output_base=$BAZEL_OUTPUT_BASE"
|
||||
|
@ -7,8 +7,8 @@ set -u -e -o pipefail
|
||||
# Publish them to npm (tagged next)
|
||||
|
||||
# We need to resolve the Bazel binary in the node modules because running Bazel
|
||||
# through `yarn bazel` causes additional output that throws off the command stdout.
|
||||
BAZEL_BIN=$(yarn bin)/bazel
|
||||
# through `yarn bazelisk` causes additional output that throws off the command stdout.
|
||||
BAZEL_BIN=$(yarn bin)/bazelisk
|
||||
# Build into a distinct output location so that artifacts from previous builds are not reused
|
||||
BAZEL_OUTPUT_BASE=$(mktemp -d -t angular-release-next.XXXXXXX)
|
||||
BAZEL="$BAZEL_BIN --output_base=$BAZEL_OUTPUT_BASE"
|
||||
|
Reference in New Issue
Block a user