[camel] branch master updated: CAMEL-11930: configured surefire not to fail th...

[zr...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

zregvart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/master by this push:
     new be8305f  CAMEL-11930: configured surefire not to fail th...
be8305f is described below

commit be8305f150ac07c7e0cf07bde56ef14f929f3244
Author: Zoran Regvart <zr...@apache.org>
AuthorDate: Mon Feb 19 08:20:52 2018 +0100

    CAMEL-11930: configured surefire not to fail th...
    
    ...e build
    
    Adds `maven.test.failure.ignore=true` option to `Test` stage so if a
    test fails in `camel-core` it will not stop tests in other modules from
    executing.
    This might give some false positives, if a module depends on changed
    functionality in `camel-core`, but it makes it easier to gather all
    failing tests in single build.
    
    This is how Maven job type used to run and I think we're more accustomed
    to it running that way.
---
 Jenkinsfile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Jenkinsfile b/Jenkinsfile
index d595718..36f92dd 100644
--- a/Jenkinsfile
+++ b/Jenkinsfile
@@ -56,7 +56,7 @@ pipeline {
 
         stage('Test') {
             steps {
-                sh "./mvnw $MAVEN_PARAMS -Pintegration -Dnoassembly test"
+                sh "./mvnw $MAVEN_PARAMS -Pintegration -Dnoassembly -Dmaven.test.failure.ignore=true test"
             }
             post {
                 always {

-- 
To stop receiving notification emails like this one, please contact
zregvart@apache.org.