Update bazel 0.14.1 (#156)

* Update to bazel 0.14.1

* limit bazel jvm heap too

Author: gregmagolan

.circleci/bazel.rc

@@ -25,3 +25,5 @@ build --experimental_repository_cache=/home/circleci/bazel_repository_cache
 # Bazel doesn't calculate the memory ceiling correctly when running under Docker.
 # Limit Bazel to consuming 3072K of RAM
 build --local_resources=3072,2.0,1.0
+# Also limit Bazel's own JVM heap to stay within our 4G container limit
+startup --host_jvm_args=-Xmx2G

.circleci/config.yml

@@ -4,7 +4,7 @@
 # We use a docker image as the basis for our build, so that all the toolchains we use
 # are already installed and the build can start running right away. It also guarantees
 # the environment is portable and reproducible on your local machine.
-var_1: &docker_image angular/ngcontainer:0.3.1
+var_1: &docker_image angular/ngcontainer:0.3.2
 
 # CircleCI lets us pick the key for storing one or more caches, to speed up subsequent builds.
 # We can use this to avoid re-fetching our dependencies from npm on every build.
@@ -13,7 +13,7 @@ var_1: &docker_image angular/ngcontainer:0.3.1
 # - the branch we are on, which really shouldn't be needed since the yarn lock file should be hermetic
 # - the docker image tag, working around an issue we saw where changing docker images causes permission
 #   errors when restoring the cache, like when the user we run as changes
-var_2: &cache_key angular-{{ .Branch }}-{{ checksum "yarn.lock" }}-0.3.1
+var_2: &cache_key angular-{{ .Branch }}-{{ checksum "yarn.lock" }}-0.3.2
 
 # Each job will inherit these defaults
 anchor_1: &job_defaults