From bf2718cebbd1c7af15c54c6da5685ed6d933cab4 Mon Sep 17 00:00:00 2001
From: Vincent Ambo <tazjin@google.com>
Date: Wed, 9 Oct 2019 13:35:39 +0100
Subject: chore(build): Use separate GCS bucket for CI runs

This has become an issue recently with changes such as GZIP
compression, where CI runs no longer work because they conflict with
the production bucket for the public instance.
---
 tools/nixery/.travis.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'tools')

diff --git a/tools/nixery/.travis.yml b/tools/nixery/.travis.yml
index 5f0bbfd3b4..31d485d728 100644
--- a/tools/nixery/.travis.yml
+++ b/tools/nixery/.travis.yml
@@ -26,7 +26,7 @@ script:
     docker run -d -p 8080:8080 --name nixery \
       -v ${PWD}/test-files:/var/nixery \
       -e PORT=8080 \
-      -e BUCKET=nixery-layers \
+      -e BUCKET=nixery-ci-tests \
       -e GOOGLE_CLOUD_PROJECT=nixery \
       -e GOOGLE_APPLICATION_CREDENTIALS=/var/nixery/key.json \
       -e GCS_SIGNING_ACCOUNT="${GCS_SIGNING_ACCOUNT}" \
-- 
cgit 1.4.1