You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by kw...@apache.org on 2022/06/03 08:51:58 UTC
[sling-tooling-jenkins] 01/01: SLING-11376 Use proper GAV for sonar-maven-plugin
This is an automated email from the ASF dual-hosted git repository.
kwin pushed a commit to branch feature/use-proper-sonar-plugin-gav
in repository https://gitbox.apache.org/repos/asf/sling-tooling-jenkins.git
commit 50dc20256408f81edf828294c70450ea58b91515
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Fri Jun 3 10:51:51 2022 +0200
SLING-11376 Use proper GAV for sonar-maven-plugin
Use fixed version to make builds reproducable
---
vars/slingOsgiBundleBuild.groovy | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/vars/slingOsgiBundleBuild.groovy b/vars/slingOsgiBundleBuild.groovy
index 56131fe..61a069c 100644
--- a/vars/slingOsgiBundleBuild.groovy
+++ b/vars/slingOsgiBundleBuild.groovy
@@ -55,7 +55,7 @@ def call(Map params = [:]) {
jdk: jenkinsJdkLabel(11, globalConfig),
publisherStrategy: 'EXPLICIT') {
try {
- sh "mvn -U clean verify sonar:sonar ${sonarcloudParams} -Pci"
+ sh "mvn -U clean verify org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184 ${sonarcloudParams} -Pci"
} catch ( Exception e ) {
// TODO - we should check the actual failure cause here, but see
// https://stackoverflow.com/questions/55742773/get-the-cause-of-a-maven-build-failure-inside-a-jenkins-pipeline/55744122