angular-docs-cn/tools/ngcontainer
Igor Minar 1faf9bbeb0 docs(dev-infra): update ngcontainer docs (#37185)
Update developer instructions by clarify and adding missing login details for the hub.docker.com image server.

PR Close #37185
2020-05-20 09:38:44 -07:00
..
Dockerfile build: update ngcontainer to bazel 0.18.0 (#26465) (#26488) 2018-10-19 20:59:29 -07:00
README.md docs(dev-infra): update ngcontainer docs (#37185) 2020-05-20 09:38:44 -07:00
publish.sh build: move ngcontainer sources to angular/angular (#23374) 2018-04-13 16:27:59 -07:00

README.md

ngcontainer

This docker container provides everything needed to build and test Angular applications:

Note: This docker image will be no longer actively updated. Consider using other Docker images that come with Node installed.

  • node 10.9.0
  • npm 6.2.0
  • yarn 1.9.2
  • Java 8 (for Closure Compiler and Bazel)
  • Bazel build tool v0.18.0 - http://bazel.build
  • Google Chrome 69.0.3497.81
  • Mozilla Firefox 47.0.1
  • xvfb (virtual framebuffer) for headless testing
  • Brotli compression utility, making smaller files than gzip

By using this, you avoid installation steps in your CI scripts and get a more consistent dev environment.

Example

See https://github.com/angular/closure-demo/blob/master/.circleci/config.yml where this container is used in CircleCI.

To run locally:

$ docker run -it --rm angular/ngcontainer

Running tests

Any program that needs to talk to a browser (eg. protractor) should be run under xvfb when executing on a headless machine like on CI. The nice way to factor this is to have your top-level test command which you run locally:

$ yarn test

Then in your CI configuration, you'd run

$ xvfb-run -a yarn test

For Developers

Install Docker on your machine in order to build/pull/push this image.

Log in to hub.docker.com as teamangular using the following command:

$ docker login

Publish a new version:

$ tools/ngcontainer/publish.sh [tag eg. 0.2.3]