Exclude JavaScript libraries from Sonar

javascript sonarqube
opticyclic picture opticyclic · Aug 31, 2012 · Viewed 13.3k times · Source

If you look at this site analysing JavaScript with Sonar you see that there are lots of errors reported on the JavaScript libraries.

http://nemo.sonarsource.org/drilldown/violations/jquery?rids%5B%5D=421365&severity=MAJOR

How can I prevent Sonar reporting the errors in the JavaScript libraries that I am using (since I can't fix any issues)?

At the same time, if I do manage to exclude the library, I don't want errors like "undefined variables" to appear in my files because they are referencing the JavaScript library.

If it makes any difference, I am using ExtJS 4.0.

Answer

Renzo Robles picture Renzo Robles · Sep 13, 2016

You can add the library as a source file exclusion inside of Analysis Scope configuration, and you should use some willcards to help you.

enter image description here

Related questions

How to tell Sonar to use my LCOV file for Code Coverage

We have a Jenkins job that contains a bunch of javascript files. We build our project via grunt, and at the end of the build we run JSCover to run our unit tests and collect code coverage. It all works. …

Read More
How to integrate sonar for a Node JS project?

I have integrated sonarqube to my Node JS project which am working and it seems to be working fine with the javascript plugin. I would like to know if there is any way we can specifically mention sonarqube to check …

Read More
Sonarqube does not retrieve my JavaScript coverage from LCOV

I have an application with the following structure: my-application +- pom.xml +- app | +- scripts | | +- app.js | | +- **/*.js | +- 3rd-party-libs +- build +- node_modules +- test I've create the pom.xml only to run the SonarQube …

Read More