iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

build: release scripts should use bazel from yarn (#26899) 

* With ec29fd3e7b, the prefix for the `bazel` command has been removed because it threw off the Bash variables. In order to fix this while still running Bazel from the `node_modules` (keeping the bazel versions consistent), we should run Bazel without Yarn (similar to how it's done for `build-packages-dist.sh`)

PR Close #26899
This commit is contained in:
Paul Gschwendtner 2018-11-01 20:47:39 +01:00 committed by Misko Hevery
parent 391767fb8f
commit 2a7210e382
2 changed files with 14 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
scripts/release/publish-latest
View File

@ -6,13 +6,17 @@ set -u -e -o pipefail
# Query Bazel for npm_package and ng_package rules with tags=["release-with-framework"] # Query Bazel for npm_package and ng_package rules with tags=["release-with-framework"]
# Publish them to npm (tagged next) # 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
# query for all npm packages to be released as part of the framework release # query for all npm packages to be released as part of the framework release
NPM_PACKAGE_LABELS=`bazel query --output=label 'attr("tags", "\[.*release-with-framework.*\]", //packages/...) intersect kind(".*_package", //packages/...)'` NPM_PACKAGE_LABELS=`${BAZEL_BIN} query --output=label 'attr("tags", "\[.*release-with-framework.*\]", //packages/...) intersect kind(".*_package", //packages/...)'`
# build all npm packages in parallel # build all npm packages in parallel
bazel build $NPM_PACKAGE_LABELS ${BAZEL_BIN} build $NPM_PACKAGE_LABELS
# publish all packages in sequence to make it easier to spot any errors or warnings # publish all packages in sequence to make it easier to spot any errors or warnings
for packageLabel in $NPM_PACKAGE_LABELS; do for packageLabel in $NPM_PACKAGE_LABELS; do
echo "publishing $packageLabel" echo "publishing $packageLabel"
bazel run -- ${packageLabel}.publish --access public --tag latest ${BAZEL_BIN} run -- ${packageLabel}.publish --access public --tag latest
done done

10
scripts/release/publish-next
View File

@ -6,12 +6,16 @@ set -u -e -o pipefail
# Query Bazel for npm_package and ng_package rules with tags=["release-with-framework"] # Query Bazel for npm_package and ng_package rules with tags=["release-with-framework"]
# Publish them to npm (tagged next) # 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
# query for all npm packages to be released as part of the framework release # query for all npm packages to be released as part of the framework release
NPM_PACKAGE_LABELS=`bazel query --output=label 'attr("tags", "\[.*release-with-framework.*\]", //packages/...) intersect kind(".*_package", //packages/...)'` NPM_PACKAGE_LABELS=`${BAZEL_BIN} query --output=label 'attr("tags", "\[.*release-with-framework.*\]", //packages/...) intersect kind(".*_package", //packages/...)'`
# build all npm packages in parallel # build all npm packages in parallel
bazel build $NPM_PACKAGE_LABELS ${BAZEL_BIN} build $NPM_PACKAGE_LABELS
# publish all packages in sequence to make it easier to spot any errors or warnings # publish all packages in sequence to make it easier to spot any errors or warnings
for packageLabel in $NPM_PACKAGE_LABELS; do for packageLabel in $NPM_PACKAGE_LABELS; do
echo "publishing $packageLabel" echo "publishing $packageLabel"
bazel run -- ${packageLabel}.publish --access public --tag next ${BAZEL_BIN} run -- ${packageLabel}.publish --access public --tag next
done done