Unable to publish Static code violations on SonarQube

[milindbangar79]

Hi,

This is the first time , I am using the plugin.

Getting the coverage, but not the code violations. Can see the voilations on Jenkins console, while the job is running.

I have the following project configurations as part of sonar-project.properties file

sonar.language=ts

the modules that SonarQube should analyze

sonar.sources=src
sonar.sourceEncoding=UTF-8
sonar.exclusions=/node_modules/,/*.spec.ts
sonar.tests=src/app
sonar.test.inclusions=/*.spec.ts
sonar.ts.tslint.configPath=tslint.json

JavaScript/TypeScript code coverage with default paths

sonar.javascript.lcov.reportPaths=report/lcov.dat
sonar.typescript.lcov.reportPaths=coverage/lcov.info

TSLint output JSON Parameter */

sonar.ts.tslint.path=node_modules/tslint/bin/tslint
sonar.typescript.node=/usr/bin/nodejs
sonar.ts.tslint.enabled=true
sonar.ts.tslint.rulesDir=node_modules/tslint-eslint-rules/dist/rules

As per documentation, you have mentioned to look out for tslint in the Jenkins Log. Do not see any except:
Starting external process node /mnt/JENKINS_HOME/workspace/CI-Ionic-App/.scannerwork/sonarts-bundle/node_modules/tslint-sonarts/bin/tsrunner

Do not see any SonarTS sensor in the log like below
INFO: Sensor TypeScript LCOV Coverage Sensor [typescript]

Am I missing anything here.

Please suggest

Regards
Milind

[ckatzorke]

What version of Sonarqube are you using?
I had the same issue - by mistake I used Sonarqube 7. When switched back to (for my use case correct) version 6.72 - it worked as expected (I am using a formerly created issue.json (by build pipeline) instead of letting sonar doing the analysis).
I had no time yet to analyze if this relates to some api change in 7, but I assume so...