[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 c63bc14  SLING-8358 - Build should not fail if a project is not 
onboarded to SonarCloud
c63bc14 is described below

commit c63bc1436eb0398a386f790d42968e01152d7e86
Author: Robert Munteanu <romb...@apache.org>
AuthorDate: Thu Apr 18 13:13:07 2019 +0300

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

diff --git a/vars/slingOsgiBundleBuild.groovy b/vars/slingOsgiBundleBuild.groovy
index 7cbcc23..c103f43 100644
--- a/vars/slingOsgiBundleBuild.groovy
+++ b/vars/slingOsgiBundleBuild.groovy
@@ -50,7 +50,7 @@ def call(Map params = [:]) {
                             publisherStrategy: 'EXPLICIT') {
                                 def output = ""
                                 try {
-                                    output = sh (script; "mvn -U clean verify 
sonar:sonar ${sonarcloudParams}", returnStdout: true).trim()
+                                    output = sh (script: "mvn -U clean verify 
sonar:sonar ${sonarcloudParams}", returnStdout: true).trim()
                                 } catch ( Exception e ) {
                                     if ( output.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."