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
After running sonar-scanner, I can't see any of the issues in Sonarqube. I just want to make sure I'm not missing anything here:
I generated a report.yml file using metric_fo (4.12). I'm using Ruby 2.1 for that. I have couple of errors with flog' and 'roodi and since both are not mandatory according to the documentation I just used the --no-roodi --no-flog option to turn them off. This successfully generated a report.yml file with issues in it.
I used sonar-scanner on the project, and the process has ended successfully, however as I mentioned - I can't see any issues on Sonarqube (I can see the files though, so the update did happen on some level). I thought that perhaps it was because I'm using the latest Sonarqube version, so I downgraded Sonaryqube and Sonar-Runner to the version you stated that work on the documentation. That didn't
do the trick either. Here's what Sonar-runner report at the end after specifying the issues:
12:33:14.255 INFO - Store results in database
12:33:14.255 DEBUG - Execute org.sonar.batch.index.MeasurePersister
12:33:14.705 DEBUG - Execute org.sonar.batch.index.DuplicationPersister
12:33:14.706 DEBUG - Execute org.sonar.batch.index.ComponentDataPersister
12:33:14.713 DEBUG - Execute org.sonar.batch.issue.IssuePersister
12:33:14.717 DEBUG - Execute org.sonar.batch.phases.GraphPersister
12:33:14.787 INFO - ANALYSIS SUCCESSFUL, you can browse http://10.150.0.31:1232/dashboard/index/jupiter_platform_gem
12:33:14.787 DEBUG - Evict preview database
12:33:14.787 DEBUG - Download: http://10.150.0.31:1232/batch_bootstrap/evict?project=1 (no proxy)
12:33:14.810 DEBUG - Post-jobs : org.sonar.plugins.core.issue.notification.SendIssueNotificationsPostJob@962dbdd -> org.sonar.plugins.core.batch.IndexProjectPostJob@39508efb -> org.sonar.plugins.dbcleaner.ProjectPurgePostJob@57db1e22
12:33:14.811 INFO - Executing post-job class org.sonar.plugins.core.issue.notification.SendIssueNotificationsPostJob
12:33:14.811 INFO - Executing post-job class org.sonar.plugins.core.batch.IndexProjectPostJob
12:33:14.828 INFO - Executing post-job class org.sonar.plugins.dbcleaner.ProjectPurgePostJob
12:33:14.840 INFO - -> Keep one snapshot per day between 2016-05-12 and 2016-06-08
12:33:14.841 INFO - -> Keep one snapshot per week between 2015-06-11 and 2016-05-12
12:33:14.842 INFO - -> Keep one snapshot per month between 2011-06-16 and 2015-06-11
12:33:14.843 INFO - -> Delete data prior to: 2011-06-16
12:33:14.853 DEBUG - ==> Preparing: select * from projects p where p.id=?
12:33:14.880 DEBUG - ==> Parameters: 1(Long)
12:33:14.892 DEBUG - <== Total: 1
12:33:14.892 DEBUG - ==> Preparing: select * from projects where scope='PRJ' and root_id=?
12:33:14.893 DEBUG - ==> Parameters: 1(Long)
12:33:14.893 DEBUG - <== Total: 0
12:33:14.893 INFO - -> Clean Jupiter Platform Gem [id=1]
12:33:14.896 INFO - <- Clean snapshot 214
12:33:15.032 DEBUG - Release semaphore on project : org.sonar.api.resources.Project@38b17a3f[id=1,key=jupiter_platform_gem,qualifier=TRK], with key batch-jupiter_platform_gem
INFO: ------------------------------------------------------------------------
INFO: EXECUTION SUCCESS
INFO: ------------------------------------------------------------------------
Total time: 15.801s
Final Memory: 30M/1426M
INFO: ------------------------------------------------------------------------
Before that he pretty much pass every error on report.yml and parse ir. Any idea what might be the issue? we are currently testing Sonarqube, could this be the reason? (even though Java issues work with the default scanner). I couldn't find where the Ruby plugin log is being saved.
The text was updated successfully, but these errors were encountered:
@amitz If it's any consolation, I've restarted work on the ruby plug-in, currently working a kink in the complexity metrics publishing but I've refactored most of the static analysis sensors with unit tests running well. Follow my fork, i'll merge the changes to master as soon as it's done.
Hello :-)
After running sonar-scanner, I can't see any of the issues in Sonarqube. I just want to make sure I'm not missing anything here:
I generated a
report.yml
file using metric_fo (4.12). I'm using Ruby 2.1 for that. I have couple of errors withflog' and 'roodi
and since both are not mandatory according to the documentation I just used the--no-roodi --no-flog
option to turn them off. This successfully generated areport.yml
file with issues in it.I used sonar-scanner on the project, and the process has ended successfully, however as I mentioned - I can't see any issues on Sonarqube (I can see the files though, so the update did happen on some level). I thought that perhaps it was because I'm using the latest Sonarqube version, so I downgraded Sonaryqube and Sonar-Runner to the version you stated that work on the documentation. That didn't
do the trick either. Here's what Sonar-runner report at the end after specifying the issues:
Before that he pretty much pass every error on report.yml and parse ir. Any idea what might be the issue? we are currently testing Sonarqube, could this be the reason? (even though Java issues work with the default scanner). I couldn't find where the Ruby plugin log is being saved.
The text was updated successfully, but these errors were encountered: