angular-cn/integration/cli-hello-world-ivy
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 refactor: correctly name `cli-hello-world-ivy` project to distinguish from `cli-hello-world` in logs (#26947) 2019-01-28 14:01:13 -08:00
src test: update cli-hello-world-ivy to cli@7.2.0-rc.0 (#27797) 2018-12-26 11:19:19 -08:00
.editorconfig test: update cli-hello-world-ivy to cli@7.2.0-rc.0 (#27797) 2018-12-26 11:19:19 -08:00
README.md test: update cli-hello-world-ivy to cli@7.2.0-rc.0 (#27797) 2018-12-26 11:19:19 -08:00
angular.json test: update cli-hello-world-ivy to cli@7.2.0-rc.0 (#27797) 2018-12-26 11:19:19 -08:00
debug-test.sh test(ivy): enable running cli-hello-world-ivy integration test suite (#27438) 2018-12-17 09:35:16 -08:00
package.json ci: pin ChromeDriver to a version compatible with docker image's Chrome (#28494) 2019-02-01 20:22:03 -05:00
tsconfig.json test: update cli-hello-world-ivy to cli@7.2.0-rc.0 (#27797) 2018-12-26 11:19:19 -08:00
tslint.json test: update cli-hello-world-ivy to cli@7.2.0-rc.0 (#27797) 2018-12-26 11:19:19 -08:00
yarn.lock build: upgrade `cli-hello-world[-ivy]` integration projects to @angular/cli@7.2.1 (#27697) 2019-01-22 12:02:10 -08:00

README.md

CliHelloWorldIvy

This project was generated with Angular CLI version 7.2.0-rc.0.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.