From 863a9b56dd766e91e84f033e3238f4bc8d014081 Mon Sep 17 00:00:00 2001 From: Dan Burkert Date: Thu, 15 Jun 2017 10:34:05 -0700 Subject: [PATCH] Skip running Java integration tests twice This is a followup to 8d2ca982fe24170c6 which reorganized the spark1/spark2 Jenkins java build. That commit inadvertently resulted in running the integration test suites for each maven project twice. Change-Id: Ia7c5e45ded6a13ca84a886b77f0065e32808b2fc Reviewed-on: http://gerrit.cloudera.org:8080/7195 Reviewed-by: Jean-Daniel Cryans Tested-by: Kudu Jenkins --- build-support/jenkins/build-and-test.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build-support/jenkins/build-and-test.sh b/build-support/jenkins/build-and-test.sh index c2c67d6ee6..a2ba47ba84 100755 --- a/build-support/jenkins/build-and-test.sh +++ b/build-support/jenkins/build-and-test.sh @@ -365,7 +365,7 @@ if [ "$BUILD_JAVA" == "1" ]; then # If there are no failures, rerun the build with Spark 1.x with Scala 2.10. # Note: this won't work if there are ever Spark integration tests! - elif ! mvn $MVN_FLAGS -Dtest="org.apache.kudu.spark.*.*" -Pspark_2.10 clean verify ; then + elif ! mvn $MVN_FLAGS -Dtest="org.apache.kudu.spark.*.*" -DskipITs -Pspark_2.10 clean verify ; then EXIT_STATUS=1 FAILURES="$FAILURES"$'Spark 1.x build/test failed\n' fi