George Kalpakas 72c36956de ci: pin ChromeDriver to a version compatible with docker image's Chrome (#28494) ... By default, `webdriver-manager update` will download the latest ChromeDriver version, which might not be compatible with the Chrome version included in the [docker image used on CI], causing CI failures. Previously, we used to pin the ChromeDriver version on CI in [ngcontainer's Dockerfile][2]. This was accidentally broken in #26691, while moving from ngcontainer to default CircleCI docker images. This commit fixes the issue by pinning ChromeDriver to a known compatible version. [1]: bfd48d156d/.circleci/config.yml (L16) [2]: bfd48d156d/tools/ngcontainer/Dockerfile (L63) PR Close #28494		2019-02-01 20:22:03 -05:00
..
e2e	build: upgrade jasmine (and related typings) to latest version (#19904)	2018-07-06 13:48:02 -07:00
src	feat(platform-browser-dynamic): export `JitCompilerFactory` (#20478)	2017-11-22 08:56:11 -06:00
index.html	feat(platform-browser-dynamic): export `JitCompilerFactory` (#20478)	2017-11-22 08:56:11 -06:00
package.json	ci: pin ChromeDriver to a version compatible with docker image's Chrome (#28494)	2019-02-01 20:22:03 -05:00
rollup.config.js	build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215)	2019-01-18 09:07:52 -08:00
rollup.lazy.config.js	build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215)	2019-01-18 09:07:52 -08:00
tsconfig.json	feat(platform-browser-dynamic): export `JitCompilerFactory` (#20478)	2017-11-22 08:56:11 -06:00
yarn.lock	build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215)	2019-01-18 09:07:52 -08:00