Skip running Java integration tests twice

This is a followup to 8d2ca98 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 <[email protected]> Tested-by: Kudu Jenkins
yubobo · Jun 16, 2017 · 863a9b5 · 863a9b5
1 parent e81db65
commit 863a9b5
Showing 1 changed file with 1 addition and 1 deletion.
diff --git 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