Changes for page SonarQube
Last modified by Boris Folgmann on 2025/11/25 10:20
To version 4.2
edited by Boris Folgmann
on 2025/11/25 10:17
on 2025/11/25 10:17
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki.s dcloud-admin-01 +xwiki:XWiki.borisfolgmannt-systemscom - Content
-
... ... @@ -19,8 +19,7 @@ 19 19 20 20 Since v3.0.0 of the [[Jenkins Shared Library>>Jenkins.Jenkins Shared Library.WebHome]], not only scanning maven projects, but also scanning all other types of projects is supported. Just use a Jenkinsfile as usual like e.g.: 21 21 22 -{{code language="none" title="**Standard invocation** 23 - "}} 22 +{{code language="none" title="**Standard invocation**"}} 24 24 @Library('sdcloud') _ 25 25 26 26 sdcPipeline() ... ... @@ -32,8 +32,7 @@ 32 32 33 33 It's possible to explicitly disable SonarQube for all branches by using a Jenkinsfile like: 34 34 35 -{{code language="none" title="**Disable SonarQube scanning** 36 - "}} 34 +{{code language="none" title="**Disable SonarQube scanning**"}} 37 37 @Library('sdcloud') _ 38 38 39 39 sdcPipeline(sonarQube: false) ... ... @@ -51,7 +51,7 @@ 51 51 sdcPipeline(defaultBranch: 'main') 52 52 {{/code}} 53 53 54 -Please note that SonarQube in the Community Edition supports only one branch per project. And this branch will always be called 'master' in the SonarQube UI even if the real name isa different one. 52 +Please note that SonarQube in the Community Edition supports only one branch per project. And this branch will always be called 'master' in the SonarQube UI even if the real name is a different one. 55 55 56 56 [[image:attach:image2022-12-6_18-27-41.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="36" width="92"]] 57 57 ... ... @@ -168,7 +168,8 @@ 168 168 1. Quality gates, which decide if a build is ok or failed. 169 169 [[image:attach:image2022-12-7_17-32-8.png||data-xwiki-image-style-border="true" queryparams="effects=drop-shadow" height="410" width="893"]] 170 170 171 -If the default settings do not fit for your instance, create a Service Request at the [[Servicedesk DevOps-as-a-Service>>https://prd.sdc.t-systems.net/jira||shape="rect"]] providing a list of users that should be part of the {{code language="none"}}sonar-quality-admins{{/code}} group. 169 +If the default settings do not fit for your instance, you can edit users in the DevOps Portal and add them that should be part of the {{code language="none"}}sonar-quality-admins{{/code}} group. 170 +[[image:1764065876906-358.png]] 172 172 173 173 The members of this group have read-write access to Quality Profiles and Quality Gates. It should be clear that you will need an internal governance so that {{code language="none"}}sonar-quality-admins{{/code}} coordinate their work and communicate with the project admins. 174 174
- 1764065876906-358.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.borisfolgmannt-systemscom - Size
-
... ... @@ -1,0 +1,1 @@ 1 +18.9 KB - Content
- DevOps%20Portal%202.1.5
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +xwiki:XWiki.borisfolgmannt-systemscom - Size
-
... ... @@ -1,0 +1,1 @@ 1 +7.9 KB - Content