Fix e2e-tests (#981)

by running them against the `dev` branch of the operators repo which is held compatible with KUDOs bleeding-edge development including breaking API changes etc.
kudobuilder · Oct 22, 2019 · f6e182f · f6e182f
1 parent f86d0d0
commit f6e182f
Showing 1 changed file with 3 additions and 2 deletions.
diff --git a/hack/run-e2e-tests.sh b/hack/run-e2e-tests.sh
@@ -15,7 +15,8 @@ then
     go run ./cmd/kubectl-kudo test --config kudo-e2e-test.yaml 2>&1 |tee /dev/fd/2 |go-junit-report -set-exit-code > reports/kudo_e2e_test_report.xml
 
 	rm -rf operators
-	git clone https://github.com/kudobuilder/operators
+	# KUDO e2e tests are executed against operators dev branch, which is held compatible with KUDOs bleeding edge
+	git clone --branch dev https://github.com/kudobuilder/operators
 	mkdir operators/bin/
 	cp ./bin/kubectl-kudo operators/bin/
 	cd operators && go run ../cmd/kubectl-kudo test 2>&1 |tee /dev/fd/2 |go-junit-report -set-exit-code > ../reports/kudo_operators_test_report.xml
@@ -25,7 +26,7 @@ else
     go run ./cmd/kubectl-kudo test --config kudo-e2e-test.yaml
 
 	rm -rf operators
-	git clone https://github.com/kudobuilder/operators
+	git clone --branch dev https://github.com/kudobuilder/operators
 	mkdir operators/bin/
 	cp ./bin/kubectl-kudo operators/bin/
 	cd operators && go run ../cmd/kubectl-kudo test