SLING-8358 - Build should not fail if a project is not onboarded to SonarCloud
Debug again
diff --git a/vars/slingOsgiBundleBuild.groovy b/vars/slingOsgiBundleBuild.groovy
index f446ab7..96f0fb5 100644
--- a/vars/slingOsgiBundleBuild.groovy
+++ b/vars/slingOsgiBundleBuild.groovy
@@ -48,11 +48,15 @@
withMaven(maven: globalConfig.mvnVersion,
jdk: jenkinsJdkLabel(jobConfig.jdks[0], globalConfig),
publisherStrategy: 'EXPLICIT') {
+ def output = ""
try {
- sh "mvn -U clean verify sonar:sonar ${sonarcloudParams}"
+ output = sh (script: "mvn -U clean verify sonar:sonar ${sonarcloudParams}", returnStdout: true).trim()
} catch ( Exception e ) {
// TODO - we should actually check here, but see https://stackoverflow.com/questions/55742773/get-the-cause-of-a-maven-build-failure-inside-a-jenkins-pipeline/55744122
// for problems with the approach
+
+ echo "OUTPUT: \n\n\n $output \n\n\n"
+
def projectNotOnboardedToSonarQube = true
if ( projectNotOnboardedToSonarQube ) {
echo "Marking build unstable due to missing SonarCloud onboarding. See https://cwiki.apache.org/confluence/display/SLING/SonarCloud+analysis for steps to fix."
