[sling-tooling-jenkins] branch master updated: SLING-8358 - Build should not fail if a project is not onboarded to SonarCloud

[rombert]

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

rombert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-tooling-jenkins.git


The following commit(s) were added to refs/heads/master by this push:
     new a73ea8e  SLING-8358 - Build should not fail if a project is not 
onboarded to SonarCloud
a73ea8e is described below

commit a73ea8eca8a439dad0a2034f5805423868337e65
Author: Robert Munteanu <romb...@apache.org>
AuthorDate: Thu Apr 18 11:59:54 2019 +0300

    SLING-8358 - Build should not fail if a project is not onboarded to 
SonarCloud
    
    Debug information
---
 vars/slingOsgiBundleBuild.groovy | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/vars/slingOsgiBundleBuild.groovy b/vars/slingOsgiBundleBuild.groovy
index 2ed02c8..cd7f6fb 100644
--- a/vars/slingOsgiBundleBuild.groovy
+++ b/vars/slingOsgiBundleBuild.groovy
@@ -51,9 +51,10 @@ def call(Map params = [:]) {
                                 try {
                                     sh "mvn -U clean verify sonar:sonar 
${sonarcloudParams}"
                                 } catch ( Exception e ) {
+                                    echo "Message is ${e.message}"
                                     if ( e.getMessage().contains("not 
authorized to run analysis")) {
                                         echo "Marking build unstable due to 
missing SonarCloud onboarding. See 
https://cwiki.apache.org/confluence/display/SLING/SonarCloud+analysis for steps 
to fix."
-                                        currentBuild.result = "UNSTABLE"
+                                        currentBuild.result = 'UNSTABLE'
                                     }
                                 }
                         }