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.
This commit is contained in:
Vincent Ambo 2019-10-09 13:35:39 +01:00 committed by Vincent Ambo
parent 2f448d5d4a
commit 1e6c3e6636

View File

@ -26,7 +26,7 @@ script:
docker run -d -p 8080:8080 --name nixery \ docker run -d -p 8080:8080 --name nixery \
-v ${PWD}/test-files:/var/nixery \ -v ${PWD}/test-files:/var/nixery \
-e PORT=8080 \ -e PORT=8080 \
-e BUCKET=nixery-layers \ -e BUCKET=nixery-ci-tests \
-e GOOGLE_CLOUD_PROJECT=nixery \ -e GOOGLE_CLOUD_PROJECT=nixery \
-e GOOGLE_APPLICATION_CREDENTIALS=/var/nixery/key.json \ -e GOOGLE_APPLICATION_CREDENTIALS=/var/nixery/key.json \
-e GCS_SIGNING_ACCOUNT="${GCS_SIGNING_ACCOUNT}" \ -e GCS_SIGNING_ACCOUNT="${GCS_SIGNING_ACCOUNT}" \