cargdev/angular
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci: build-packages-dist.sh should publish only regular and --compile=local packages (#26471)

Browse Source 
We don't need to publish JIT compiled packages as this is not useful for real-world use-cases.

PR Close #26471
This commit is contained in:
Igor Minar 2018-10-22 19:43:13 -07:00 committed by Alex Rickabaugh
parent 57531737e5
commit 5952775a03
1 changed files with 4 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
scripts/build-packages-dist.sh
View File

@ -30,7 +30,7 @@ echo "##################################"
[ -d "${basedir}/${destPath}" ] || mkdir -p $basedir/${destPath} [ -d "${basedir}/${destPath}" ] || mkdir -p $basedir/${destPath}
dirs=`echo "$targets" | grep '//packages/[^/]*:npm_package' | sed -e 's/\/\/packages\/\(.*\):npm_package/\1/'` dirs=`echo "$targets" | sed -e 's/\/\/packages\/\(.*\):npm_package/\1/'`
for pkg in $dirs; do for pkg in $dirs; do
# Skip any that don't have an "npm_package" target # Skip any that don't have an "npm_package" target
@ -49,8 +49,8 @@ echo "##################################"
# packages in their deps[]. # packages in their deps[].
# Until then, we have to manually run bazel first to create the npm packages we # Until then, we have to manually run bazel first to create the npm packages we
# want to test. # want to test.
LEGACY_TARGETS=`bazel query --output=label 'kind(.*_package, //packages/...)'` BAZEL_TARGETS=`bazel query --output=label 'attr("tags", "\[.*release-with-framework.*\]", //packages/...) intersect kind(".*_package", //packages/...)'`
buildTargetPackages "$LEGACY_TARGETS" "dist/packages-dist" "legacy" "Production" buildTargetPackages "$BAZEL_TARGETS" "dist/packages-dist" "legacy" "Production"
# We don't use the ivy build in the integration tests, only when publishing # We don't use the ivy build in the integration tests, only when publishing
# snapshots. # snapshots.
@ -61,15 +61,7 @@ buildTargetPackages "$LEGACY_TARGETS" "dist/packages-dist" "legacy" "Production"
|| "${CIRCLE_PROJECT_REPONAME-}" != "angular" || "${CIRCLE_PROJECT_REPONAME-}" != "angular"
]] && exit 0 ]] && exit 0
# TODO: do we actually need to query for jit and local targets? shouldn't this be all the packages that we publish to npm?
IVY_JIT_TARGETS=`bazel query --output=label 'attr("tags", "\[.*ivy-jit.*\]", //packages/...) intersect kind(".*_package", //packages/...)'`
IVY_LOCAL_TARGETS=`bazel query --output=label 'attr("tags", "\[.*ivy-local.*\]", //packages/...) intersect kind(".*_package", //packages/...)'`
# A clean is needed since build artifacts from previous build can break the following build # A clean is needed since build artifacts from previous build can break the following build
bazel clean bazel clean
buildTargetPackages "$IVY_JIT_TARGETS" "dist/packages-dist-ivy-jit" "jit" "Ivy JIT" buildTargetPackages "$BAZEL_TARGETS" "dist/packages-dist-ivy-local" "local" "Ivy AOT"
# A clean is needed since build artifacts from previous build can break the following build
bazel clean
buildTargetPackages "$IVY_LOCAL_TARGETS" "dist/packages-dist-ivy-local" "local" "Ivy AOT"