From cb28ed1f95d34eb3ca4199d39498882f52b7735d Mon Sep 17 00:00:00 2001 From: Ke Wu Date: Fri, 2 Jun 2017 14:52:01 -0700 Subject: [PATCH] Let COS docker validation node tests against gci-next-canary We plan to use family gci-next-canary in container-vm-image-staging for future Docker upgration and validation. --- .../docker_validation/cos-docker-validation.properties | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/test/e2e_node/jenkins/docker_validation/cos-docker-validation.properties b/test/e2e_node/jenkins/docker_validation/cos-docker-validation.properties index 6b7b269a3f8..b5a996d2738 100644 --- a/test/e2e_node/jenkins/docker_validation/cos-docker-validation.properties +++ b/test/e2e_node/jenkins/docker_validation/cos-docker-validation.properties @@ -1,5 +1,5 @@ -GCI_IMAGE_PROJECT=cos-docker-validation -GCI_IMAGE_FAMILY=validation-test +GCI_IMAGE_PROJECT=container-vm-image-staging +GCI_IMAGE_FAMILY=gci-next-canary GCI_IMAGE=$(gcloud compute images describe-from-family ${GCI_IMAGE_FAMILY} --project=${GCI_IMAGE_PROJECT} --format="value(name)") GCI_CLOUD_INIT=test/e2e_node/jenkins/gci-init.yaml