angular-cn

Commit Graph

Author	SHA1	Message	Date
Paul Gschwendtner	391767fb8f	build: fix size artifacts not measured by github robot (#27042 ) Currently the Github robot is not able to measure the artifacts of the `hello_world` and `todo` bundling tests because those will be only built with the `ivy-only` rule tag. This means that the current CircleCI job that is supposed to upload the size artifacts, does not even build those bundles. PR Close #27042	2018-11-20 10:44:12 -08:00
Wei Huang	5241ea086d	test(bazel): Run Angular test on RBE (#25370 ) PR Close #25370	2018-09-18 13:29:54 -07:00
Wei Huang	c8b70ae8e4	build(bazel): Run build-packages-dist on RBE (#25237 ) PR Close #25237	2018-08-20 16:34:45 -07:00
Greg Magolan	dd44f63c73	build(bazel): show bazel progress in CircleCI to prevent 10m timeout with no output (#24663 ) PR Close #24663	2018-07-26 17:02:21 -07:00
Alex Eagle	580f05bd9c	build: flatten esm5 sources before rollup (#23131 ) this is needed to update to latest rules_nodejs due to breaking change in https://github.com/bazelbuild/rules_nodejs/pull/172 It has the side-effect of correctly marking rxjs packages as side-effect-free PR Close #23131	2018-04-03 10:47:29 -07:00
Alex Eagle	8407fcc979	ci: double our cores on CircleCI (#22641 ) This should cut our build time in ~half, assuming it's widely parallel. See https://circleci.com/docs/2.0/configuration-reference/#resource_class Also enable bazel repository caching, and store the external repositories in the CircleCI cache for later builds. PR Close #22641	2018-03-07 21:00:03 -08:00
Alex Eagle	8ec21fc325	ci: enable bazel remote caching on CircleCI (#21784 ) This should cause Bazel builds to be incremental, only re-building parts of Angular affected by changes since the last build. It also fixes a potential version skew, where CI was running the Bazel linter binaries in the ngcontainer docker image, but developers built them using the versions in WORKSPACE PR Close #21784	2018-02-13 10:10:41 -08:00

7 Commits