ci: make sure it is a tagged build before doing tagged things

stephenplusplus · stephenplusplus · commit 0ff331200c36 · 2017-03-23T09:06:14.000-04:00
diff --git a/scripts/circle/post-test.sh b/scripts/circle/post-test.sh
@@ -26,19 +26,22 @@ fi
 
 # For a tagged build, we will build the docs for the associated module.
 # Otherwise, it will build for master.
-export TAGGED_MODULE_NAME=$(node -p "process.env.CIRCLE_TAG.replace(/-\d.*/, '')")
-export TAGGED_MODULE_VERSION=${CIRCLE_TAG/*-}
-
-if [ "${CIRCLE_TAG:0:1}" == "v" ]
+if [ "${CIRCLE_TAG}" != "" ]
 then
-  export TAGGED_MODULE_NAME="google-cloud"
-  export TAGGED_MODULE_VERSION=${CIRCLE_TAG:1}
-fi
+  export TAGGED_MODULE_NAME=$(node -p "process.env.CIRCLE_TAG.replace(/-\d.*/, '')")
+  export TAGGED_MODULE_VERSION=${CIRCLE_TAG/*-}
 
-if [ "${TAGGED_MODULE_NAME:0:6}" == "common" ]
-then
-  echo "This module does not require documentation to be built."
-  exit 0
+  if [ "${CIRCLE_TAG:0:1}" == "v" ]
+  then
+    export TAGGED_MODULE_NAME="google-cloud"
+    export TAGGED_MODULE_VERSION=${CIRCLE_TAG:1}
+  fi
+
+  if [ "${TAGGED_MODULE_NAME:0:6}" == "common" ]
+  then
+    echo "This module does not require documentation to be built."
+    exit 0
+  fi
 fi
 
 set +e # allows `git` commands during prepare-ghpages to fail
