angular-docs-cn/scripts
Paul Gschwendtner 31116f0ced ci: re-enable material unit tests job (#33530)
The Material units tests job has been disabled with the
typescript upgrade PR since the components repository was
still on an old TypeScript version (due to cyclic dependencies
between the framework and components repository).

Since the components repository has been updated to `9.0.0-next.15`
and now uses the compatible TypeScript version, we can re-enable
ds

Related to this change, we need to ignore the `package.json`
engines when installing the dependencies of the components repo. This
is because the components repo already updated to NodeJS v12 and Yarn
v1.19.1. This is not the case for the CI setup of framework. For now,
since we don't want to change the dev setup (as it slows down
development), we temporarily disable the engines.

Additionally, the material unit tests job now depends on the actual
release packages (not on the ngtsc compiled ones). This is because
the components repo setup relies on NGCC being run. This is also
helpful for validating ngcc against the framework packages.

PR Close #33530
2019-11-01 17:38:39 +00:00
..
browserstack
ci ci: re-enable material unit tests job (#33530) 2019-11-01 17:38:39 +00:00
git build: mention where to find the invalid commit message, when validation fails (#32420) 2019-08-30 13:52:54 -04:00
github build: update base SHA for rebase on merge-pr script 2019-05-21 17:07:19 -07:00
jenkins
local-dev build: address comments, restructure setup-rbe.sh script (#33109) 2019-10-21 15:56:52 -04:00
release build: ensure that version stamping is applied when the npm_package publish action is called (#33512) 2019-10-31 10:21:41 -07:00
saucelabs ci: move bazel saucelabs execution to script to be used across all Angular repos (#32141) 2019-08-16 09:57:23 -07:00
build-ivy-npm-packages.sh
build-packages-dist.sh
package-builder.sh ci: run bazel for package-builder via yarn rather than binary directly (#32983) 2019-10-10 13:57:54 -07:00