Bump Windows cache (digital-asset#7056)

The "output was not created" errors seem to have become very frequent. While taking out nodes seems to work as a bandaid, I’d like to see if resetting the cache buys us a few days of not having to deal with this. Admittedly, I don’t really have an explanation for why resetting the cache should help if taking out the machines seems to do something (suggesting that it hasn’t propagated fully). changelog_begin changelog_end
kgeonw · Aug 7, 2020 · 31c2ce0 · 31c2ce0
1 parent 15bbd9a
commit 31c2ce0
Show file tree

Hide file tree

Showing 4 changed files with 8 additions and 1 deletion.
diff --git a/build.ps1 b/build.ps1
@@ -49,6 +49,9 @@ function bazel() {
 # which is a workaround for this problem.
 bazel shutdown
 
+# Temporary, remove once cache reset is complete
+bazel clean --expunge
+
 # Prefetch nodejs_dev_env to avoid permission denied errors on external/nodejs_dev_env/nodejs_dev_env/node.exe
 # It isn’t clear where exactly those errors are coming from.
 bazel fetch @nodejs_dev_env//...

diff --git a/ci/configure-bazel.sh b/ci/configure-bazel.sh
@@ -74,7 +74,7 @@ if is_windows; then
   SUFFIX="${SUFFIX:0:3}"
   echo "Platform suffix: $SUFFIX"
   # We include an extra version at the end that we can bump manually.
-  CACHE_SUFFIX="$SUFFIX-v7"
+  CACHE_SUFFIX="$SUFFIX-v8"
   CACHE_URL="$CACHE_URL/$CACHE_SUFFIX"
   echo "build:windows-ci --remote_http_cache=https://bazel-cache.da-ext.net/$CACHE_SUFFIX" >> .bazelrc.local
 fi

diff --git a/compatibility/build-release-artifacts-windows.ps1 b/compatibility/build-release-artifacts-windows.ps1
@@ -37,6 +37,8 @@ function bazel() {
 
 
 bazel shutdown
+# Temporary, remove once cache reset is complete
+bazel clean --expunge
 bazel fetch @nodejs_dev_env//...
 bazel build `
   `-`-experimental_execution_log_file ${ARTIFACT_DIRS}/build_execution_windows.log `

diff --git a/compatibility/test-windows.ps1 b/compatibility/test-windows.ps1
@@ -45,6 +45,8 @@ cd compatibility
 cp ../.bazelrc .bazelrc
 
 bazel shutdown
+# Temporary, remove once cache reset is complete
+bazel clean --expunge
 bazel fetch @nodejs_dev_env//...
 bazel build //...
 bazel shutdown