0b348c8ffe
build: fix bazel stamping ( #22965 )
...
As pointed out in https://github.com/bazelbuild/rules_nodejs/issues/156
our mechanism would never pick up changes to the version info.
PR Close #22965
2018-03-28 09:00:02 -07:00
2a1e3d191f
docs: add info about the WebStorm plugin to BAZEL.md ( #22572 )
...
PR Close #22572
2018-03-05 21:24:23 -08:00
2654357c72
docs: update BAZEL.md crosstool error instructions ( #22018 )
...
PR Close #22018
2018-02-18 13:18:54 -08:00
bba65e0f41
feat(bazel): introduce a binary stamping feature ( #22176 )
...
This grabs version control metadata and makes it available in the build, eg. to put in the version field for released artifacts
PR Close #22176
2018-02-15 14:08:53 -08:00
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
c878d55397
docs: add VSCode interaction issue to bazel docs ( #22128 )
...
PR Close #22128
2018-02-09 17:13:06 -08:00
11b12670b2
docs: document debugging a Node test in VSCode/Bazel ( #21868 )
...
PR Close #21868
2018-01-29 16:11:09 -08:00
0de219adcd
docs(bazel): document an installation issue ( #21401 )
...
observed by Igor on a Mac
PR Close #21401
2018-01-10 12:23:39 -08:00
c66283ad66
build: add istruction for running and debugging tests to `BAZEL.md` ( #21053 )
...
PR Close #21053
2017-12-22 13:10:51 -08:00
f48b343af1
build: switch from npm to yarn ( #19328 )
...
PR Close #19328
2017-09-22 13:20:52 -07:00
0317c4c478
build: update bazel rules to latest ( #18289 )
2017-07-21 18:09:44 -05:00
7c479f073e
docs: document using Bazel ( #17701 )
2017-07-11 12:48:50 -07:00
Alex Eagle
Igor Minar
Miško Hevery
Victor Berchet
Alex Eagle
Olivier Combe