Paul Gschwendtner 8fc4ae51fb build: use bazel version from node modules (#26691) ... * No longer depends on a custom CircleCI docker image that comes with Bazel pre-installed. Since Bazel is now available through NPM, we should be able to use the version from `@bazel/bazel` in order to enforce a consistent environment on CI and locally. * This also reduces the amount of packages that need to be published (ngcontainer is removed) PR Close #26691		2018-10-30 16:19:13 -04:00
..
browserstack	ci: clean up CI logging, folding, add build time logging, and improve error handling (#14425)	2017-03-02 00:22:24 -08:00
ci	build: clean up *.gz files created by payload-size.sh (#26746)	2018-10-25 21:17:52 -04:00
git	refactor: add a commit-msg git hook to check commit messages (#22969)	2018-03-26 18:34:31 -04:00
github	build: add more labels to review-pr script (#26493)	2018-10-16 14:36:28 -07:00
jenkins	fix(build): make perf tests work again	2015-02-27 15:22:19 -08:00
release	build: use bazel version from node modules (#26691)	2018-10-30 16:19:13 -04:00
sauce	build: switch from npm to yarn (#19328)	2017-09-22 13:20:52 -07:00
windows	build: fix windows scripts (#23121)	2018-07-12 16:42:56 -04:00
build-packages-dist.sh	build: use bazel version from node modules (#26691)	2018-10-30 16:19:13 -04:00