updating angular cli to my fork

.appveyor.yml

@@ -1,21 +1,24 @@
 environment:
-  matrix:
-    - nodejs_version: "6"
+  nodejs_version: "10.9.0" # Same version as used in CircleCI.
 
 matrix:
   fast_finish: true
 
 install:
   - ps: Install-Product node $env:nodejs_version
-  - npm install -g npm@~5.3.0
-  - npm install
+  # --network-timeout is a workaround for https://github.com/yarnpkg/yarn/issues/6221
+  - yarn --frozen-lockfile --network-timeout=500000
+  - yarn webdriver-update-appveyor
 
 test_script:
   - node --version
-  - npm --version
-  - node tests\run_e2e.js --appveyor
+  - yarn --version
+  - yarn test
+  - node tests\legacy-cli\run_e2e.js --appveyor "--glob=tests/{basic,commands,generate,build/styles}/**"
 
 build: off
+deploy: off
 
 cache:
-  - node_modules -> package-lock.json
+  - node_modules -> yarn.lock
+  - "%LOCALAPPDATA%\\Yarn"

.circleci/bazel.rc

@@ -0,0 +1,20 @@
+# These options are enabled when running on CI
+# We do this by copying this file to /etc/bazel.bazelrc at the start of the build.
+
+# Echo all the configuration settings and their source
+build --announce_rc
+
+# Don't be spammy in the logs
+build --noshow_progress
+
+# Don't run manual tests
+test --test_tag_filters=-manual
+
+# Workaround https://github.com/bazelbuild/bazel/issues/3645
+# Bazel doesn't calculate the memory ceiling correctly when running under Docker.
+# Limit Bazel to consuming resources that fit in CircleCI "medium" class which is the default:
+# https://circleci.com/docs/2.0/configuration-reference/#resource_class
+build --local_resources=3072,2.0,1.0
+
+# Retry in the event of flakes
+test --flaky_test_attempts=2