Paul Gschwendtner 2ce5ffd56b build: no longer use bazel from "ngcontainer" image ...

We no longer use Bazel from the `ngcontainer` image as it is
no longer maintained and we need to use the latest version of
Bazel in CircleCI. It's not ideal to use Bazel through Yarn since
binaries like that should be actually part of the docker image, but
for now we need to do this for jobs that use NodeJS & Bazel at the same time.
This is similar to what `angulart/angular` does.

2019-06-21 09:34:21 -07:00

..

bazel

cleanup: rename lib/ to material/ (#15889)

2019-04-24 09:53:00 -07:00

browserstack

build: ensure tunnel identifiers are unique (#14108)

2018-11-14 14:19:22 -08:00

caretaking

chore: update "material2" to "components" (#15905)

2019-04-25 13:19:41 -07:00

circleci

build: no longer use bazel from "ngcontainer" image

2019-06-21 09:34:21 -07:00

deploy

ci: fix snapshots (#15908)

2019-04-25 16:26:47 -07:00

saucelabs

build: downgrade to sauce-connect v4.5.1 (#28659) (#15183)

2019-02-13 17:13:45 -08:00