sonar-cxx 0.9.2 doesn't show technical debt with sonar 4.5.1 #464
Comments
|
I think the common rules have no sqale parameters at the moment since they On Wed, Apr 15, 2015, 04:57 diaguo [email protected] wrote:
|
|
hi, thanks |
|
For those ones you should have some values yes, try to look when you On Wed, Apr 15, 2015, 10:54 diaguo [email protected] wrote:
|
|
hi, thanks [CP_Codec_ALL_SONAR_TR] $ /workspace/workspace_hzbtsci/tools/hudson.plugins.sonar.SonarRunnerInstallation/sonar166/bin/sonar-runner -Dsonar.jdbc.url=jdbc:mysql://10.69.22.55:5800/so2?autoReconnect=true&useUnicode=true&characterEncoding=utf8 -Dsonar.host.url=http://hzbtsci.xxxxxxxx.net:9000 -Dsonar.projectBaseDir=/workspace/workspace_hzbtsci/workspace/CP_Codec_ALL_SONAR_TR -Dsonar.sourceEncoding=UTF-8 -Dsonar.cxx.coverage.reportPath=gcovr-reports/ -Dsonar.sources=SS_Codec,SS_CommonDsp/CP_TupFrameProtocol,SS_LocalOam,SS_LocalTelecom,SS_W1plTx,SS_WcdmaEngineDrivers/CP_L1Transmission,SS_WcdmaEngineDrivers/CP_DecoderDriver -Dsonar.language=c++ -Dsonar.junit.reportsPath=gcovr-reports/ -Dsonar.projectVersion=1.0 -Dsonar.projectKey=DSP_CP_Codec_ALL_UT_TR:Trunk -Dsonar.verbose=false -Dsonar.cxx.includeDirectories=include/Codec_Env,/usr/include/,/usr/include/linux,/usr/include/sys,SS_CommonDsp/ -Dsonar.cxx.coverage.itReportPath=gcovr-reports/ -Dsonar.scm.url=scm:svn:https://beisop60.xxxxx.net/isource/svnroot/BTS_SC_DSP/trunk/workarea/C_Application/SC_DSP -Dsonar.cxx.coverage.overallReportPath=gcovr-reports/ -Dsonar.projectName=DSP_CP_Codec_ALL_UT_TR |
|
2015.04.15 16:14:12 INFO web[org.sonar.INFO] Deploy GWT plugins... from above logs, seems server start normally. |
|
By the way you mention Cppcheck.exe. the plugin does not run any external On Wed, Apr 15, 2015, 11:11 diaguo [email protected] wrote:
|
|
but in previous sonar version, a technical debt plugin will get the technical debt value by just use sonar-cxx plugin for analysis, But builtin technical debt shows 0 issues and Technical Debt 0.0 days. |
|
so builtin technical debt need issues for value, issues need external tool to generate them. |
|
correct, please take a look on the changes introduced in the sonar platform On Wed, 15 Apr 2015 at 11:32 diaguo [email protected] wrote:
|
|
hi, jmecosta |
|
you will need to enable the correspondent rules that take care of All this you can try if you build 0.9.3 snapshot. 0.9.2 does not contain On Thu, 16 Apr 2015 at 08:14 diaguo [email protected] wrote:
|
|
hi, thank you again, by enable the rules in the Common SonarQube repository. there are issues but no technical debt value. |
|
hi, do you mean i can try 0.9.3 snapshot as 0.9.2 doesn't show technical debt. |
|
Current planning is to release RC1 on Sunday and final by end of April.
|
|
Hi, thanks, I need to upgrade sonar server to 4.5.2? Guo Dianwu From: ext Günter Wirth [mailto:[email protected]] Current planning is to release RC1 on Sunday and final by end of April.
— |
|
Yes, 0.9.3 is using 4.5.2 API which is no more compatible to 4.5 and 4.5.1.
|
|
we will have it updated against 4.5.4 since its the last LTS, right? |
|
Hi, thanks again, Guo Dianwu From: ext Günter Wirth [mailto:[email protected]] Yes, 0.9.3 is using 4.5.2 API which is no more compatible to 4.5 and 4.5.1.
— |
|
no, this is a core feature. unless you want to write your own plugin with your own model it cant be done. |
|
For compatibility see https://travis-ci.org/wenns/sonar-cxx/builds/58412347
|
|
so all issues need supported by plugin then can calculate technical debt value? sonar core can‘t deal with those report files directly for issues, right? |
|
Correct On Thu, Apr 16, 2015, 11:08 diaguo [email protected] wrote:
|
|
OK. |
|
No problem On Thu, Apr 16, 2015, 11:20 diaguo [email protected] wrote:
|
|
hi, thanks again, Duplicated blocks the following is old plugin algorithm. Violations = cost_to fix_one_violation * mandatory_violations Comments = cost_to_comment_one_API * public_undocumented_api Coverage = cost_to_cover_one_of_complexity * uncovered_complexity_by_tests (80% of coverage is the objective) Complexity = cost_to_split_a_method * (function_complexity_distribution >= 8) + cost_to_split_a_class * (class_complexity_distribution >= 60) |
|
Personally I prefer also the old way. I see no benefit in this new Sqale classification. But the old way is no more supported by the core. Please write a feature request in the SQ forum.
|
|
hi, sorry for need help again. Complexity = cost_to_split_a_method * (function_complexity_distribution >= 8) + cost_to_split_a_class * (class_complexity_distribution >= 60) |
|
There are complexity rules in the sonarqube-c++ repo. Function 2 complex On Wed, Apr 29, 2015, 10:15 diaguo [email protected] wrote:
|
|
thanks! i have tried it and it works well! |
hi, from the SonarQube-compatibility-matrix. the latest version only support sonar 4.5.1, right?
i use the above version for build. and enabled rules in Cppcheck 321 RATS 300 Vera++ 27 Valgrind 15 c++ Common SonarQube 6 Repositories. And build find some issues which belong to c++ Common SonarQube rules. technical debt shows issues are 274 but 0 technical debt value(sqale_index).
is the cxx plugin not support sonar sqale or not compatiable with Common SonarQube rules?
Thanks in advance and waiting for your answers!
The text was updated successfully, but these errors were encountered: