ci(docs-infra): "test_aio_local_ivy" job should attach ivy package output (#29117)

Currently the "test_docs_examples_ivy" job attaches
the legacy package output, while we can also attach
the Ivy NPM package output. We don't need Ngcc to downlevel
the Angular packages in order to build AIO with Ivy.

PR Close #29117
This commit is contained in:
Paul Gschwendtner 2019-03-05 19:12:31 +01:00 committed by Andrew Kushnir
parent b446095c4d
commit 69265b7b5d
1 changed files with 7 additions and 1 deletions

View File

@ -305,6 +305,12 @@ jobs:
steps: steps:
- *attach_workspace - *attach_workspace
- *init_environment - *init_environment
# Rename the Ivy packages dist folder to "dist/packages-dist" as the AIO
# package installer picks up the locally built packages from that location.
# *Note*: We could also adjust the packages installer, but given we won't have
# two different folders of Angular distributions in the future, it's likely not
# worth the efforts to change the AIO packages installer.
- run: mv dist/packages-dist-ivy-aot dist/packages-dist
# Build aio with Ivy (using local Angular packages) # Build aio with Ivy (using local Angular packages)
- run: yarn --cwd aio build-with-ivy --progress=false - run: yarn --cwd aio build-with-ivy --progress=false
@ -597,7 +603,7 @@ workflows:
- build-npm-packages - build-npm-packages
- test_aio_local_ivy: - test_aio_local_ivy:
requires: requires:
- build-npm-packages - build-ivy-npm-packages
- test_aio_tools: - test_aio_tools:
requires: requires:
- build-npm-packages - build-npm-packages