sonar-maven-plugin reports about a missed quality gate but the sonarqube frontend does not show the issues
We run the org.sonarsource.scanner.maven:sonar-maven-plugin:3.5.0.1254 with the "sonar" goal and get
build 28-Nov-2018 13:10:03 [INFO] Quality gate status: ERROR
build 28-Nov-2018 13:10:03 [ERROR] Unit Test Failures: 5 > 0
build 28-Nov-2018 13:10:03 [ERROR] Critical Issues: 75 > 0
build 28-Nov-2018 13:10:03 [ERROR] [BUILD BREAKER] Project did not meet 2 conditions
("Critical Issues: 75 > 0" is a bit imprecise since the quality gate is "critical issues over leak period is greater than 0")
We expect to see these 75 issues in the sonarqube frontend but they are not displayed there although the dashboard for our project shows the failed quality gate condition with a link containing
resolved=false&severities=CRITICAL&sinceLeakPeriod=true
The 75 issues are displayed with
severities=CRITICAL&sinceLeakPeriod=true
All are resolved.
So, the problems seems to be with the sonar-maven-plugin which does not recognize the issues as being resolved.
What are we doing wrong?
Our sonarqube version is 6.7.5 (build 38563).
Best regards
Achim
maven plugins sonarqube
asked Nov 28 '18 at 14:11
Achim AbelingAchim Abeling
112
add a comment |
We run the org.sonarsource.scanner.maven:sonar-maven-plugin:3.5.0.1254 with the "sonar" goal and get
build 28-Nov-2018 13:10:03 [INFO] Quality gate status: ERROR
build 28-Nov-2018 13:10:03 [ERROR] Unit Test Failures: 5 > 0
build 28-Nov-2018 13:10:03 [ERROR] Critical Issues: 75 > 0
build 28-Nov-2018 13:10:03 [ERROR] [BUILD BREAKER] Project did not meet 2 conditions
("Critical Issues: 75 > 0" is a bit imprecise since the quality gate is "critical issues over leak period is greater than 0")
We expect to see these 75 issues in the sonarqube frontend but they are not displayed there although the dashboard for our project shows the failed quality gate condition with a link containing
resolved=false&severities=CRITICAL&sinceLeakPeriod=true
The 75 issues are displayed with
severities=CRITICAL&sinceLeakPeriod=true
All are resolved.
So, the problems seems to be with the sonar-maven-plugin which does not recognize the issues as being resolved.
What are we doing wrong?
Our sonarqube version is 6.7.5 (build 38563).
Best regards
Achim
maven plugins sonarqube
asked Nov 28 '18 at 14:11
Achim AbelingAchim Abeling
112
Perhaps sonarqube simply just don't work like I expected. We now (hopefully) fixed it by using another condition. Before we used the condition "Critical issues" with the "Over leak period" flag enabled. Now we use "new critical issues".
– Achim Abeling
Nov 30 '18 at 8:58
add a comment |
We run the org.sonarsource.scanner.maven:sonar-maven-plugin:3.5.0.1254 with the "sonar" goal and get
build 28-Nov-2018 13:10:03 [INFO] Quality gate status: ERROR
build 28-Nov-2018 13:10:03 [ERROR] Unit Test Failures: 5 > 0
build 28-Nov-2018 13:10:03 [ERROR] Critical Issues: 75 > 0
build 28-Nov-2018 13:10:03 [ERROR] [BUILD BREAKER] Project did not meet 2 conditions
("Critical Issues: 75 > 0" is a bit imprecise since the quality gate is "critical issues over leak period is greater than 0")
We expect to see these 75 issues in the sonarqube frontend but they are not displayed there although the dashboard for our project shows the failed quality gate condition with a link containing
resolved=false&severities=CRITICAL&sinceLeakPeriod=true
The 75 issues are displayed with
severities=CRITICAL&sinceLeakPeriod=true
All are resolved.
So, the problems seems to be with the sonar-maven-plugin which does not recognize the issues as being resolved.
What are we doing wrong?
Our sonarqube version is 6.7.5 (build 38563).
Best regards
Achim
maven plugins sonarqube
asked Nov 28 '18 at 14:11
Achim AbelingAchim Abeling
112
We run the org.sonarsource.scanner.maven:sonar-maven-plugin:3.5.0.1254 with the "sonar" goal and get
build 28-Nov-2018 13:10:03 [INFO] Quality gate status: ERROR
build 28-Nov-2018 13:10:03 [ERROR] Unit Test Failures: 5 > 0
build 28-Nov-2018 13:10:03 [ERROR] Critical Issues: 75 > 0
build 28-Nov-2018 13:10:03 [ERROR] [BUILD BREAKER] Project did not meet 2 conditions
("Critical Issues: 75 > 0" is a bit imprecise since the quality gate is "critical issues over leak period is greater than 0")
We expect to see these 75 issues in the sonarqube frontend but they are not displayed there although the dashboard for our project shows the failed quality gate condition with a link containing
resolved=false&severities=CRITICAL&sinceLeakPeriod=true
The 75 issues are displayed with
severities=CRITICAL&sinceLeakPeriod=true
All are resolved.
So, the problems seems to be with the sonar-maven-plugin which does not recognize the issues as being resolved.
What are we doing wrong?
Our sonarqube version is 6.7.5 (build 38563).
Best regards
Achim
maven plugins sonarqube
maven plugins sonarqube
asked Nov 28 '18 at 14:11
Achim AbelingAchim Abeling
112
asked Nov 28 '18 at 14:11
Achim AbelingAchim Abeling
112
edited Nov 28 '18 at 14:19
Achim Abeling
asked Nov 28 '18 at 14:11
Achim AbelingAchim Abeling
112
asked Nov 28 '18 at 14:11
Achim AbelingAchim Abeling
112
asked Nov 28 '18 at 14:11
Achim AbelingAchim Abeling
112
112
Perhaps sonarqube simply just don't work like I expected. We now (hopefully) fixed it by using another condition. Before we used the condition "Critical issues" with the "Over leak period" flag enabled. Now we use "new critical issues".
– Achim Abeling
Nov 30 '18 at 8:58
add a comment |
Perhaps sonarqube simply just don't work like I expected. We now (hopefully) fixed it by using another condition. Before we used the condition "Critical issues" with the "Over leak period" flag enabled. Now we use "new critical issues".
– Achim Abeling
Nov 30 '18 at 8:58
Perhaps sonarqube simply just don't work like I expected. We now (hopefully) fixed it by using another condition. Before we used the condition "Critical issues" with the "Over leak period" flag enabled. Now we use "new critical issues".
– Achim Abeling
Nov 30 '18 at 8:58
Perhaps sonarqube simply just don't work like I expected. We now (hopefully) fixed it by using another condition. Before we used the condition "Critical issues" with the "Over leak period" flag enabled. Now we use "new critical issues".
– Achim Abeling
Nov 30 '18 at 8:58
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53521386%2fsonar-maven-plugin-reports-about-a-missed-quality-gate-but-the-sonarqube-fronten%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53521386%2fsonar-maven-plugin-reports-about-a-missed-quality-gate-but-the-sonarqube-fronten%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Perhaps sonarqube simply just don't work like I expected. We now (hopefully) fixed it by using another condition. Before we used the condition "Critical issues" with the "Over leak period" flag enabled. Now we use "new critical issues".
– Achim Abeling
Nov 30 '18 at 8:58