Remove HTTP Trigger (ingress) tests in the GKE scenario

vmware-archive · Mar 28, 2018 · a954695 · a954695
1 parent a0cd091
commit a954695
Showing 1 changed file with 4 additions and 1 deletion.
diff --git a/.travis.yml b/.travis.yml
@@ -138,7 +138,10 @@ script:
           echo "Waiting for a previous installation to be cleaned"
           bash -c 'grep -q "No resources found" <(timeout 60 kubectl get pods -n kubeless -w 2>&1)'
         fi
-        ./script/integration-tests gke_${GKE_PROJECT}_${ZONE}_${ESCAPED_GKE_CLUSTER}
+        ./script/integration-tests gke_${GKE_PROJECT}_${ZONE}_${ESCAPED_GKE_CLUSTER} deployment
+        ./script/integration-tests gke_${GKE_PROJECT}_${ZONE}_${ESCAPED_GKE_CLUSTER} basic
+        ./script/integration-tests gke_${GKE_PROJECT}_${ZONE}_${ESCAPED_GKE_CLUSTER} cronjob
+        ./script/integration-tests gke_${GKE_PROJECT}_${ZONE}_${ESCAPED_GKE_CLUSTER} kafka
         ;;
       esac
     else