Sonarqube 4.1.2 with the latest php-plugin is not detecting any violations.
When I run the analisis with Sonar 4.2 it shows me the errors how I expected them.
Is there a bug related to the php-plugin? Can anyone confirm this behaviour?
Thanks in advance
When using SonarQube 4.1.2, could you double check the content of the PHP quality profile that you're using ? Indeed in latest versions of the PHP plugin, all rules have been rewritten so if you have also upgraded the PHP plugin perhaps you're simply doing an analysis with an empty quality profile.
Related
In the documentation (https://docs.sonarqube.org/latest/extend/adding-coding-rules/#header-1) TypeScript isn't listed as a supported language for custom rules but JavaScript is. Because of this is it possible to use the JavaScript runner to execute custom TypeScript rules?
If not, is anyone aware of how to do more advanced rules with tslint or is there an alternative to SonarQube that would allow it?
for SonarQube visit here and here, it will help you.
and I found this, it’s not possible, the concept of external issues
appeared in SonarQube 7.2. Upgrade to the new LTS 7.9
I'm working in the sonarqube 3.7.4. I analysed my java project and it clearly showing me the number of issues with the count. But while clicking the issues it results in "No matching issues found".
Please provide me the suggestion to fix the issues
You should upgrade to the latest LTS version of SonarQube : 4.5.6
I'm trying to use SonarQube Eclipse plugin (version 3.4) along with SonarQube version 3.7.4, Eclipse Kepler and a mulit-modules maven project and I'm facing the following issue.
After having run a local analysis (in preview mode as incremental mode is not possible with 3.7.4) , all issues appear twice. I checked their properties and see that I have for each issue A the following :
A1. issue that is created before the local analysis (probably taken from server)
A2. issue that is added after the local analysis
Both are marked in the view as being "old issues" (new issue = false.)
If I add new issues, they are correctly added to the list. However if I fix an old issue, A2 is removed but A1 still remains in the view (which is rather annoying).
Am I doing something wrong ? Is there a way in order to have only issues displayed once ?
Note : the Eclipse project is correctly associated to the SonarQube component (I'm working with multi-modules projects)
Thank you in advance,
This is a know bug that is referenced here: SONARIDE-426
Feel free to watch it and vote for it.
It is possible turn off some issue checking in sonar projects and how to do it? I want to for example disable "Tabulation characters should not be used" or "Modifier Order".
Thank for help.
If you would like keep the rule active while excluding certain parts of your source-code, you can use features of the the switch-off violations-plugin.
The plugin was deprecated with sonarqube 4.0, as it is now possible to use integrated features described in this part of the sonarqube-documentation:
http://docs.codehaus.org/display/SONAR/Narrowing+the+Focus
If you are using an older version of sonarqube you find the plugin here:
http://docs.codehaus.org/display/SONAR/Switch+Off+Violations+Plugin
I have upgraded my sonar version from sonar-3.2 to sonar-3.5.1 and upgraded sonar-runner from sonar-runner-1.1 to sonar-runner-2.2.2, now when i am deploying project on newly installed sonar 3.5.1 it run successfully and showing ANALYSIS SUCCESSFUL, it also show project name on sonar server when i use localhost:9000 on browser but code is not showing there, no violations are coming etc.
i am using sonar in two ways and both results the same. Two ways are:
1. using sonar standalone through sonar runner from cmd.
2. integrating sonar with Jenkins(1.515) and using maven(3.0.4)
when i do sonar analysis on sonar 3.2 everything is working fine in both of the above cases but problem comes only when i use sonar 3.5.1.
Can anybody help me out on this issue??
Please suggest what would be the possible way to overcome this issue..
your revert will be appreciable.. Thanks in advance!!
Please refer below for logs
and sonar dashboard
So I do confirm that the Sonar Java plugins have been deleted from the extensions/plugins directory and that's why you don't get any measures/violations when analysing a java project. Here is the link to download version 1.2 of the Sonar Java plugin ecosystem : http://docs.codehaus.org/download/attachments/230396085/JavaEcosystem-1.2.zip. You just have to decompress this archive, place all jar(s) in the extensions/plugins directory and relaunch the Sonar server.