I have verified SonarQube + jacoco analyzer's integration test coverage using v 6.1 and jacoco maven plugin 0.7.7.201606060606
This works as expected and is able to list coverage by integration tests.
We have a SonarQube server running at version 5.1.1 does anyone know if that version of SonarQube is capable of showing integration test coverage numbers when using agents at 0.7.7.201606060606?
Reading JaCoCo report is done by the sonar java analyzer (so the sonarqube version is a rather indirect information here).
JaCoCo produces binary report and last incompatibility introduced was in 0.7.6 and that was handled in sonar java analyzer 3.4.
So if you use any version of SonarQube with a java analyzer with a version greater than 3.4 you should be fine to analyze JaCoCo reports produced with version 0.7.7
However given that 5.1.1 is not the latest LTS I would recommend you to upgrade to at least 5.6 and use latest sonar java analyzer.
Related
The sonar.branch parameter is deprecated starting from SonarQube 6.7.
Will branch analysis on Sonar for Bamboo still function after upgrading to Sonarqube 6.7 without having the branch plugin?
Yes, the plug-in still supports the old branching model even with version 6.7.
Am using SonarQube 5.1.2 and Java Version 1.7.45. The SonarQube scanner 3.0.3 is only compatible with Java 8 and SonarQube v5.6.
How to analyse my code, using SonarQube 5.1.2 with the scanner? How to get a scanner for SonarQube 5.1.2?
The official sonar scanner documentation page is a confluence page, with a "page history" (click on ... at the right top of the page).
When going back in history, I found out, that the version of June, 2nd 2017 refers to SonarQube Scanner 2.6.1 – Compatible with SonarQube 4.5.4+ (LTS).
The download link of that page is still valid, you can download the old scanner there.
But btw: I strongly recommend to update. SonarQube 5.1 is no longer maintained and later SonarQube version have a lot of improvements!
In our Sonar Build Environment we use SonarQube Server Version 5.6.6 (64-Bit) and our analysis runs on a Sonar Client Build Operating System with Ubuntu 14.04.5 LTS (64-Bit).
Recently I have upgraded SonarQube from 5.1 to 5.6.6 (LTS). But under "Project Code" the "Customize ON|OFF" option is now missing.
Currently I can see only these options:
Lines of Code
Bugs
Vulnerabilities
Code Smells
Coverage
Duplications
In SonarQube version 5.1 I was using the "Customize ON|OFF" option to customize and add required columns.
How can I enable this feature back in SonarQube 5.6.6?
The feature does not exist any longer (it has been dropped when rewriting the Project space), and there's currently no plan to reintroduce it.
The Governance plugin is not working with the version. And pdf-report plugin is also not supported.
There is currently no option that we are aware of.
You are right that Governance is indeed not compatible with SonarQube 6.3.1 because it's not a LTS (Long Term Supported) version - and Governance is released only for LTS versions of SonarQube.
We are using SonarQube 5.1 and want to upgrade to SonarQubee 5.2 or 5.3 due to some issues around issue assign area of SonarQube 5.1
We are also using SonarQube eclipse plugin 3.5.0
I noticed recently that SonarQube eclipse plugin 3.5.0 is not supported with SonarQube 5.2 as per http://docs.sonarqube.org/display/SONAR/SonarQube+in+Eclipse.
Also latest SonarLint release 1.2 cannot connect to remote Sonar Instance to fetch server rules. This feature was available with SonarQube eclipse plugin 3.5.0.
I found on Stackoverflow that SonarLint would support this feature with release 2.0 but there is no planned release date for 2.0
Getting remote config file for SonarLint if online, using local if offline
My question is why SonarQube ecosystem upgrades are not synchronised?
SonarQube eclipse plugin should support latest SonarQube releases until SonarLint is capable to connect to remote Sonar instance to fetch server rules.
How anyone who are supposed to take SonarQube upgrades to resolve problems with existing version could execute eclipse analysis?
As you have read, the SonarQube Eclipse plugin has been deprecated in favor of SonarLint for Eclipse. One of the main reasons behind this is that SonarLint for Eclipse is designed to be an independant product which lifecycle must be decoupled from SonarQube - in order to ease and speed up innovation on the user experience in the IDE. So by now, SonarQube and SonarLint upgrades are not synchronized by definition.
Still, your question is perfectly valid: why don't we make some last updates on the SQ Eclipse plugin as long as SonarLint is not able to connect to a SonarQube server? The main reason is that we believe so much in SonarLint that we want to focus all our attention and energy on that product, and therefore we want to move fast to be able to have the "connected-to-SonarQube" experience as soon as possible. Our telemetry tells us that most existing users and customers are currently using a SonarQube version that is still usable with the SQ Eclipse plugin, so I feel this is the right decision to work as fast as possible on SonarLint to make sure it can connect to a SonarQube instance in the upcoming months (when the next LTS is released).
The following combination works fine
(SonarLint + SonarScanner + SonarQube + Eclipse):
SonarLint: 3.5.0.201804241315
sonarScanner: sonar-scanner-3.2.0.1227-windows
SonarQube: 6.7.4 (build 38452)
sonar-scanner.properties:
sonar.host.url=http://localhost:9000
sonar.sourceEncoding=UTF-8
sonar.projectKey=JavaProject
sonar.projectName=MyJavaStandaloneProject
sonar.projectVersion=0.0.1-SNAPSHOT
sonar.sources=D:/eclipse/workspace/MyJavaStandaloneProject
sonar.java.binaries=D:/eclipse/workspace/MyJavaStandaloneProject/target/classes
pom.xml:
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>sonar-maven-plugin</artifactId>
<version>3.2</version>
</plugin>
</plugins>
</build>
Bind Eclipse projects to SonarQube projects:
Select a SonarQube server: localhost
Eclipse Project: MyJavaStandaloneProject
SonarQube Project: 'MyJavaProject' on server localhost
Click: Auto bind selected projects.
"Note: SonarQube Project: 'MyJavaProject' on server localhost
can be auto configured by clicking Auto bind button."
All configurations done.
Right click project and Run As Maven build ...
Goal: sonar:sonar
[INFO] ANALYSIS SUCCESSFUL