You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This discussion was converted from issue #132 on February 15, 2023 16:42.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Jenkins and plugins versions report
Jenkins: 2.375.1
sonar: 2.15
sonar-gerrit: 377.v8f3808963dc5
SonarQube: Version 9.8 (build 63668)
What Operating System are you using (both controller, and any agents involved in the problem)?
CentOS 7
Reproduction steps
Hello,
We are using SonarQube, Jenkins, and Gerrit. I'm trying to troubleshoot inconsistent issue reporting between our dev and prod environments.
I've been scanning the same changeset in both dev and prod. In both cases, SonarQube finds one issue.
In prod, that issue is reported back to Gerrit.
In dev, no issues are reported back to Gerrit.
I've tried scanning multiple projects in our dev environment, but all report 0 issues back to Gerrit.
This must be a configuration issue, but from what I can tell, both environments are identical.
Any insights on how to troubleshoot this would be much appreciated. It's not clear to me exactly how Sonar Gerrit retrieves issues from SonarQube.
Thank you for your time.
Bryan
Expected Results
SonarQube task 'xxxxxxxxxxxxxxxx' completed.
Issues to be commented: 1
Issues to be involved in score calculation: 1
Review has been sent
Actual Results
SonarQube task 'xxxxxxxxxxxxxxxx' completed.
Issues to be commented: 0
Issues to be involved in score calculation: 0
Review has been sent
Anything else?
No response
Beta Was this translation helpful? Give feedback.
All reactions