Parameters to configure project analysis can be set in various multiple places. Here is the hierarchy of parameters:
- Global analysis parameters, defined in the UI, will apply to all the projects (From the top bar, go to Settings > General Settings)
- Project analysis parameters, defined in the UI, will override global parameters (At project level, go to Configuration > Settings)
- Project analysis parameters, defined in a project analysis configuration file or in an analyzer configuration file, will override the ones defined in the UI
- Analysis / Command line parameters, defined when launching an analysis, will override project analysis parameters
sonar.profileparameter via command line for a specific project, it will not be stored in the database. Then, a local analysis Local analyses in Eclipse will , for example, would still be run against the default quality profile.
The project key that is unique for each project.
Name of the project that will be displayed on the web interface.
The project version.
Set the language of the source code . If a plugin allows to analyze another language, the associated source code analyser can be activated with this property.
Comma-separated paths to directories containing sourcessource files.
Description of the The project description.
Comma-separated paths to directories containing binaries (in the binary files (directories with class files, in the case of Java: directories with class files).
Comma-separated paths to directories containing tests.
Comma-separated paths to files with third-party libraries (JAR files in the case of Java: JAR files). Pattern Patterns can be used.
Note that the * wildcard character is not supported for directories (, only for files).
This property is used by rule engines during issues detection (mainly the SonarQube engine and FindBugs engines, which both rely on bytecode). Having the bytecode of these libraries allows the rules engines to get more information on coupling, possible null parameters when calling external APIs, etc. and , thus getting more accuracy during issues issue detection.
Set the analysis mode. See Concepts.
Set the source file encoding.
Encoding of source files. Example of values: UTF-8, MacRoman, Shift_JIS. This property can be replaced by the standard property
The list of available encodings depends on your JVM. See http://docs.oracle.com/javase/1.5.0/docs/guide/intl/encoding.doc.html.
Allow or suppress the import of the text of source files into SonarQube.
For security or other reasons , there are times when project sources must not be stored and displayed. Set this value to false to prevent the text of a project's source files from being available via the SonarQube interface to anyone at all.
When starting to analyze a Assign a date to the analysis.
Note: This parameter is applicable to a few, special use cases, rather than being an "every day" parameter:
To answer those use cases, you can use the sonar.projectDate property. Format The format is
The process is the following:
Note: first analyze the latest version and then move You must analyze your versions in chronological order to the newest one, oldest first.
Exclude files from analysis. See Project Administration for more details. This page also details
Some project modules should not be analyzed and consolidated with global project measures, for instance samples, integration tests or generated code.
Comma-separated list of the modules to analyse, all other modules are automatically ignored. Be careful: the root project must be added to the list.
Manage SCM branches. Two branches of the same project are considered as to be different projects in SonarQube.
Override the profile that would normally be used to analyze a project.
Through the web interface, you can define as many quality profiles as you want, and you can easily associate one of these quality profiles to a given project though the web interface.
Default profile for the given language
To skip Skip the computation of design metrics and dependencies.
Currently only available for Java.
When SonarQube needs a Maven phase or goal to be executed prior to the analysis, this parameter can be used. For example
Dynamic analysis relates to unit tests. By default (
See the Code Coverage by Unit Tests tutorial for details and examples.
To set Set the working directory for an analysis triggered with the SonarQube Runner or the SonarQube Ant Task (versions greater than 2.0).
Path must be relative and unique for each project.
Beware: the specified folder is deleted before running each analysis.
Increasing HTTP timeouts of requests to server. The Maven plugin executes some HTTP requests to the server. Two timeouts makes the call fails if the server connection is too slow. In such a case the timeouts can be increased from Maven properties.
Respectively 30,000 and 60,000 milliseconds
Exclusions / Inclusions
See Narrowing the Focus to:
- Exclude files from analysis
- Prevent some files from being checked for duplications
- Prevent some files from being taken into account for code coverage by unit tests and integration tests
- Ignore issues on certain components and against certain coding rules
|Display logs to know see where the analyzer spends time is spent.|
|Display all the SQL requests executed on batch sidequeries executed by the analyzer.|
|Display the result results of all the SQL requests executed on batch sidequeries executed by the analyzer.|
|Activation of the Activate DEBUG mode on batch sidefor the analyzer.|