And to learn more about controlling the scope of your analysis, see the page on Narrowing the focus.Ĭomma-separated paths to directories containing main source files.

For language-specific parameters related to external issue reports, see external issues. Most of the property keys shown in the interface at both global and project levels can also be set as analysis parameters, but the parameters listed below can only be set at analysis time.įor language-specific parameters related to test coverage and execution, see test coverage. Subsequent analyses, or analyses in SonarLint with connected mode, would still be executed with the exclusions defined in the UI and therefore stored in the DB. For example, if you override the sonar.exclusions parameter via the command line for a specific project, it will not be stored in the database. Note that only parameters set through the UI are stored in the database. Analysis / Command line parameters: Defined when launching an analysis with -D on the command line.Project analysis parameters: Defined in a project analysis configuration file or scanner configuration file.At project level, defined in the UI in Project Settings > General Settings Project properties: Apply to one project only.Defined in the UI in Administration > Configuration > General Settings Global properties: Apply to all projects.

Sonarqube phpstorm