From c93a9ff0cabaae0d16e0050690cf6594e8cf780d Mon Sep 17 00:00:00 2001 From: Ismael Juma Date: Sat, 1 Sep 2018 11:15:49 -0700 Subject: [PATCH] MINOR: Pass `--continue` to gradle in jenkins.sh This ensures that the whole test suite is executed even if there are failures. It currently stops at a module boundary if there are any failures. There is a discussion to change the gradle default to stop after the first test failure: https://github.com/gradle/gradle/issues/6513 `--continue` is recommended for CI in that discussion. Author: Ismael Juma Reviewers: Dong Lin Closes #5599 from ijuma/jenkins-script-continue --- jenkins.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jenkins.sh b/jenkins.sh index f3ec91bf676..b03195eb5b0 100755 --- a/jenkins.sh +++ b/jenkins.sh @@ -17,4 +17,4 @@ # This script is used for verifying changes in Jenkins. In order to provide faster feedback, the tasks are ordered so # that faster tasks are executed in every module before slower tasks (if possible). For example, the unit tests for all # the modules are executed before the integration tests. -./gradlew clean compileJava compileScala compileTestJava compileTestScala checkstyleMain checkstyleTest findbugsMain unitTest rat integrationTest --no-daemon -PxmlFindBugsReport=true -PtestLoggingEvents=started,passed,skipped,failed "$@" +./gradlew clean compileJava compileScala compileTestJava compileTestScala checkstyleMain checkstyleTest findbugsMain unitTest rat integrationTest --no-daemon --continue -PxmlFindBugsReport=true -PtestLoggingEvents=started,passed,skipped,failed "$@"