commit b72c254ccbe7d578eabb6dd77da4b3bc070c3849
author Dale LaBossiere <dlaboss@us.ibm.com> Mon Oct 23 14:55:38 2017 -0400
committer Dale LaBossiere <dlaboss@us.ibm.com> Mon Oct 23 14:55:38 2017 -0400
tree b60457aae9e4c6d697c73376ad06dc3b7c2fa401
parent 5365c4f56173912c0c4aef36939e5b10de50b78c

switch jenkins mvn to use --fail-at-end

Typically expect things to work since they passed the git j8 pull check.
We seem to see a variety of transient (I think test host load releated)
failures.  With fail-at-end maybe we can at least get a better sense of
the magnitude of this.

Jenkinsfile

diff --git a/Jenkinsfile b/Jenkinsfile
index f537374..07ed98f 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -37,6 +37,7 @@
     } else {
         mavenLocalRepo = "-Dmaven.repo.local=.repository"
     }
+    def mavenFailureMode = "--fail-at-end"  // vs --fail-fast
 
     try {
         stage ('Cleanup') {
@@ -51,12 +52,12 @@
 
         stage ('Build') {
             echo 'Building'
-            sh "${mvnHome}/bin/mvn ${mavenLocalRepo} -Pplatform-android,platform-java7,distribution,toolchain -Djava8.home=${env.JAVA_HOME} -Dedgent.build.ci=true clean ${mavenGoal} sonar:sonar site:site"
+            sh "${mvnHome}/bin/mvn ${mavenFailureMode} ${mavenLocalRepo} -Pplatform-android,platform-java7,distribution,toolchain -Djava8.home=${env.JAVA_HOME} -Dedgent.build.ci=true clean ${mavenGoal} sonar:sonar site:site"
         }
 
         stage ('Stage Site') {
             echo 'Staging Site'
-            sh "${mvnHome}/bin/mvn ${mavenLocalRepo} -Pplatform-android,platform-java7,distribution,toolchain -Djava8.home=${env.JAVA_HOME} -Dedgent.build.ci=true site:stage"
+            sh "${mvnHome}/bin/mvn ${mavenFailureMode} ${mavenLocalRepo} -Pplatform-android,platform-java7,distribution,toolchain -Djava8.home=${env.JAVA_HOME} -Dedgent.build.ci=true site:stage"
         }
 
     }