sonarqube5.1

I have set up SonarQube, Maven and Cobertura to upload unit test coverage at every build run. I want to use the differential views to get coverage for the delta (new code only). The coverage itself is successfully uploaded, and I can see the delta in lines of code. However, I can't get the "Coverage on new Code" to work. I tried different values for the leak period, including previous_analysis and previous_version (changing the version from 1.0 to 1.1 in the new analysis). I also used -Dsonar.projectDate to simulate a past date of analysis but still no luck. Any thoughts? The key requirement

A lot of our build jobs fail at the moment as of the "Insufficient privileges" problem since the update to 5.x. The problem should be fixed in SonarQube 5.1 as stated in here but either it is in fact not fixed or there is another problem with the same error as we currently run SonarQube 5.1.1. Here's an example of the error message: 08:27:13 [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.6:sonar (default-cli) on project server: Fail to decorate 'org.sonar.api.resources.File@b77a66[key=src/main/java/ch/ti8m/security/hwtoken/server/services/impl/TOTPAlgorithm.java,path=src

This is about sonarqube 5.1 version I have issue assign plugin and also subscribed to the emails in my profile page. I've done some erroneous SVN commits deliberately to check the email notification settings but it doesn't seem to work correctly. I receive emails sometimes but other times it doesn't work like that. I know this is not a constructive enough question but I'm really stucked here after trying all the scenarios and going through the documentation. Any insight would be highly appreciated. You should uninstall this plugin. It is compatible, but it does not work correctly. The problem

We are using sonarqube 5.1.1 and often the step "Apply project exclusions" is very, very slow. In the range of 1-2.5 hours sometimes. We have "Global Source File Exclusions" to exclude 2 patterns: **/swagger-ui/** **/*.min.js I'm not sure how recent a change this is because our sonarqube builds are run nightly. Update: I did a thread dump as requested and it looks like it's waiting on an db connection. Full thread dump Java HotSpot(TM) Server VM (24.79-b02 mixed mode): "pool-2-thread-1" prio=10 tid=0x9e43cc00 nid=0x6e88 waiting on condition [0xa0151000] java.lang.Thread.State: TIMED_WAITING

Scenario: I am migrating our current VS Solution analysis setup from using the sonar-runner to using the MSBuild runner. However I am encountering a fairly significant problem. In the old setup, we specified our project name, key and most importantly a long list of skipped projects ( sonar.visualstudio.skippedProjectPattern ) using the sonar-project.properties file. This is because [WARNING: ugly legacy bad coding practice alert] we have six solutions that build dozens and dozens of projects, all out of the same git repo. A lot of the projects are common across several solutions and we don't

I recently upgraded my SonarQube server from 4.5.2 to 5.0.1, then to 5.1 (see edit below). Suddenly, the analysis of a multi-module Maven project failed with the following error : [INFO] [12:02:05.045] Sensor SCM Sensor... [INFO] [12:02:05.169] SCM provider for this project is: svn [INFO] [12:02:05.169] Retrieve SCM blame information... [INFO] [12:02:05.185] 650 files to be analyzed [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] myproject ......................................... FAILURE [3:21.165s] [INFO] module1 .........