-
Notifications
You must be signed in to change notification settings - Fork 106
it always report zero bug but running tslint separately will show a lot of issues #172
Comments
You've set a project path in your sonar-project.properties, it seems from the log? i.e. you'll have a key somewhere
If you're specifying projectPath, you need to specify the full path to the project's |
Here is my
Now I have commented out the The result is still the same: |
The Jenkins log could be found at https://gist.github.com/greenlaw110/0515201a48c25d5661a0d4c878c5a54c |
I am experiencing the same result. My sonarqube version is 5.6.6 and sonar scanner version is 3.0.3.778. Any help would be appreciated. |
Same problem here with same versions than @Jeferex. |
Any updates on this? Facing the same problem. |
The solution I found to this was the following:
Example snip of sonar-project.properties:
In the above example, I am using a linux install and I am pointing to the actual binary for nodejs and tslint. |
@CINJ I followed your instructions, but it still doesn't work for me. It's like there are no files being analysed. Here's the part about typescript in my console when running in debug mode:
|
Same here, @CINJ solution did'nt worked as expected. |
You need to post your tslint.json file, your sonar-project properties file to help me understand the problem. The issues I faced were twofold:
To help debug the issues yourself, see if you can run TSLINT directly from the command line on your project. If that works perperly, then you can move back up the chain to the sonar-plugin and make sure it's configuration is correct. Regards |
I've got the same problem. I try to run sonar-scanner with (tslint: v5.8.0, tslint-sonarts: v1.6.0 and sonarqube-scanner: v2.0.2) - and it seems that no tslint rules have been checked. If I run tslint separately from command-line, broken rules can be found. Here's the relevant snipped of my sonar-project.properties
I already tried to set the following paths explicit but still no errors:
What am I doing wrong? |
Hi, I facing the same problem is there any update on it ? Thanks |
Here is my
sonar-project.properties
:My sonar-scanner version
My sonarqube version is
5.6.3
Running
sonar-scanner -X
generated the following outputs:The text was updated successfully, but these errors were encountered: