parent
b0d86c1c2f
commit
26a15cc534
|
@ -50,10 +50,19 @@ echo "##################################"
|
|||
# Until then, we have to manually run bazel first to create the npm packages we
|
||||
# want to test.
|
||||
LEGACY_TARGETS=`bazel query --output=label 'kind(.*_package, //packages/...)'`
|
||||
buildTargetPackages "$LEGACY_TARGETS" "dist/packages-dist" "legacy" "Production"
|
||||
|
||||
# We don't use the ivy build in the integration tests, only when publishing
|
||||
# snapshots.
|
||||
# This logic matches what we use in the .circleci/config.yml file to short-
|
||||
# circuit execution of the publish-packages job.
|
||||
[[ -v CIRCLE_PR_NUMBER
|
||||
|| "$CIRCLE_PROJECT_USERNAME" != "angular"
|
||||
|| "$CIRCLE_PROJECT_REPONAME" != "angular"
|
||||
]] && exit 0
|
||||
|
||||
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/...)'`
|
||||
|
||||
buildTargetPackages "$LEGACY_TARGETS" "dist/packages-dist" "legacy" "Production"
|
||||
buildTargetPackages "$IVY_JIT_TARGETS" "dist/packages-dist-ivy-jit" "jit" "Ivy JIT"
|
||||
buildTargetPackages "$IVY_LOCAL_TARGETS" "dist/packages-dist-ivy-local" "local" "Ivy AOT"
|
||||
|
||||
|
|
Loading…
Reference in New Issue