Alex Eagle 08aa54e1d9 ci: Add back the CLI integration test with pinning (#21555) ... The CLI app is now checked in, rather than generated dynamically with `ng new`. This loses some assertion power, but gains hermeticity. It also checks in lock files for all integration tests, avoiding floating version numbers. We'll need another place to integration test between changes in the various repositories - but the angular/angular PR-blocking status is not the right place to do this. PR Close #21555		2018-01-25 22:18:55 -08:00
..
src	build: upgrade bazel rules to latest (#20768)	2017-12-07 11:27:50 -08:00
.bazelrc	test: Enable sass compiler for bazel integration test (#19357)	2017-09-26 09:44:47 -07:00
angular.tsconfig.json	build(common): don't generate tsickle re-export file for locales package (#19135)	2017-09-21 16:02:40 -07:00
BUILD.bazel	build: upgrade bazel rules to latest (#20768)	2017-12-07 11:27:50 -08:00
package.json	ci: Add back the CLI integration test with pinning (#21555)	2018-01-25 22:18:55 -08:00
WORKSPACE	build: Update to latest rules_typescript. (#21675)	2018-01-22 15:32:59 -08:00
yarn.lock	ci: Add back the CLI integration test with pinning (#21555)	2018-01-25 22:18:55 -08:00