![sonar 8.5 vst scan subfolder sonar 8.5 vst scan subfolder](https://docplayer.net/docs-images/71/64984613/images/33-0.jpg)
Read from build system for Maven, Gradle, MSBuild projects. Defaults to project base directory when neither sonar.sources nor sonar.tests is provided.Ĭomma-separated paths to directories containing test source files.
![sonar 8.5 vst scan subfolder sonar 8.5 vst scan subfolder](https://user-images.githubusercontent.com/10205854/43384198-982ba9aa-93dd-11e8-8676-1dc7f176f816.png)
Modifying this value from the default is useful only when you're experiencing timeouts during analysis while waiting for the server to respond to Web Service calls.Ĭomma-separated paths to directories containing main source files. Maximum time to wait for the response of a Web Service call (in seconds).
#Sonar 8.5 vst scan subfolder password#
If you're using a login, this is the password that goes with your sonar.login username. If you're using an authentication token, leave this blank. The authentication token or login of a SonarQube user with Execute Analysis permission on the project. When authentication is required or the "Anyone" pseudo-group does not have permission to perform analyses, you'll need to supply the credentials of a user with Execute Analysis permissions for the analysis to run under. Authentication is enforced in the global Security(/instance-administration/security/) settings. for Maven projects, otherwise "not provided"īy default, user authentication is required to prevent anonymous users from browsing and analyzing projects on your instance, and you need to pass these parameters when running analyses. If not provided and there is already a name in the DB, it won't be overwritten for Maven projects, otherwise project key. Name of the project that will be displayed on the web interface. Allowed characters are: letters, numbers, -, _. 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 & Execution.įor language-specific parameters related to external issue reports, see External Issues.Īnalysis parameters are case-sensitive. 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. Note that only parameters set through the UI are stored in the database.įor example, if you override the sonar.exclusions parameter via command line for a specific project, it will not be stored in the database. Analysis / Command line parameters, defined when launching an analysis (with -D on the command line), override project analysis parameters.Project analysis parameters, defined in a project analysis configuration file or scanner configuration file, override the ones defined in the UI.
![sonar 8.5 vst scan subfolder sonar 8.5 vst scan subfolder](https://docplayer.net/docs-images/53/31116277/images/28-0.png)
Project properties, defined in the UI, override global property values (At a project level, go to Project Settings > General Settings).Global properties, defined in the UI, apply to all projects (From the top bar, go to Administration > Configuration > General Settings).Project analysis settings can be configured in multiple places.