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 7af2b9b Revert "SLING-8358 - Build should not fail if a project is
not onboarded to SonarCloud"
7af2b9b is described below
commit 7af2b9b5517f1cc78d258d5af097cd09a14ccc1e
Author: Robert Munteanu <[email protected]>
AuthorDate: Thu Apr 18 14:08:46 2019 +0300
Revert "SLING-8358 - Build should not fail if a project is not onboarded to
SonarCloud"
This reverts commit 12c95e5551f6817dd96cbbf716bae0368ae0680c.
---
vars/slingOsgiBundleBuild.groovy | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/vars/slingOsgiBundleBuild.groovy b/vars/slingOsgiBundleBuild.groovy
index 96f0fb5..f446ab7 100644
--- a/vars/slingOsgiBundleBuild.groovy
+++ b/vars/slingOsgiBundleBuild.groovy
@@ -48,15 +48,11 @@ def call(Map params = [:]) {
withMaven(maven: globalConfig.mvnVersion,
jdk: jenkinsJdkLabel(jobConfig.jdks[0],
globalConfig),
publisherStrategy: 'EXPLICIT') {
- def output = ""
try {
- output = sh (script: "mvn -U clean verify
sonar:sonar ${sonarcloudParams}", returnStdout: true).trim()
+ sh "mvn -U clean verify sonar:sonar
${sonarcloudParams}"
} 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."
