Use separate go test caches for config and config-next

letsencrypt · Nov 4, 2023 · 078c37b · 078c37b
1 parent 1d31a22
commit 078c37b
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/docker-compose.next.yml b/docker-compose.next.yml
@@ -4,4 +4,5 @@ services:
     environment:
       FAKE_DNS: 10.77.77.77
       BOULDER_CONFIG_DIR: &boulder_config_dir test/config-next
+      GOCACHE: /boulder/.gocache/go-build-next
       GOFLAGS: -mod=vendor
diff --git a/docker-compose.yml b/docker-compose.yml
@@ -9,6 +9,7 @@ services:
       # FAKE_DNS: 172.17.0.1
       FAKE_DNS: 10.77.77.77
       BOULDER_CONFIG_DIR: test/config
+      GOCACHE: /boulder/.gocache/go-build
       GOFLAGS: -mod=vendor
       # Forward the parent env's GOEXPERIMENT value into the container.
       GOEXPERIMENT: ${GOEXPERIMENT}