Use the new remote cache on the data server
This points to data-fast so we can move it around however at a future
time easily with DNS magic. This is a 10 Gbps link to a bazel-remote
instance running a gRPC cache. This should cache lockless queue test
once and for all.
Change-Id: Iaee7b2471d7eed668ffd83d379f9f154658b4b24
Signed-off-by: Austin Schuh <austin.linux@gmail.com>
diff --git a/tools/build_rules/js.bzl b/tools/build_rules/js.bzl
index eb95510..55f440b 100644
--- a/tools/build_rules/js.bzl
+++ b/tools/build_rules/js.bzl
@@ -102,6 +102,9 @@
name = "_app",
srcs = srcs,
deps = deps + APPLICATION_DEPS,
+ tags = [
+ "no-remote-cache",
+ ],
visibility = ["//visibility:private"],
)
@@ -110,6 +113,9 @@
name = "_polyfills",
srcs = ["polyfills.ts"],
deps = ["//:node_modules/zone.js"],
+ tags = [
+ "no-remote-cache",
+ ],
visibility = ["//visibility:private"],
)
esbuild(
@@ -123,6 +129,9 @@
metafile = False,
format = "esm",
minify = True,
+ tags = [
+ "no-remote-cache",
+ ],
visibility = ["//visibility:private"],
)
@@ -200,6 +209,9 @@
["--scripts", "--module", "%s/main.js" % bundle],
# The input HTML template, all assets for potential access for stamping
srcs = [":index.html", ":%s" % bundle, ":polyfills-bundle"] + html_assets,
+ tags = [
+ "no-remote-cache",
+ ],
visibility = ["//visibility:private"],
)
@@ -304,6 +316,9 @@
terser_minified(
name = name + "__min",
srcs = [name + ".js"],
+ tags = [
+ "no-remote-cache",
+ ],
sourcemap = False,
)