# requiredRequired metadata sonar.projectKey=my:project sonar.projectName=My project sonar.projectVersion=1.0 # optionalPaths description sonar.projectDescription=Fake description # path to source directories (requiredto source directories. # Paths are relative to the sonar-project.properties file. Replace "\" by "/" on Windows. # Do not put the "sonar-project.properties" file in the same directory with the source code. # (i.e. never set the "sonar.sources" property to ".") sonar.sources=srcDir1,srcDir2srcDir # The value of the property must be the key of the language. sonar.language=cobol # Encoding of the source code sonar.sourceEncoding=UTF-8 # Additional parameters sonar.my.property=value
Since SonarQube 3.7, any Any user who's granted Execute Analysis permission can run an analysis.
If the Anyone group is not granted Execute Analysis permission or if the SonarQube instance is secured (the
sonar.forceAuthentication property is set to
true), the credentials of a user having been granted Execute Analysis permission have to be provided through the
sonar.password properties. Example:
sonar-runner -Dsonar.login=myLogin -Dsonar.password=myPassword
SonarQube 3.4 to 3.6.3
From SonarQube 3.4 to 3.6.3, if If a project cannot be accessed anonymously, the
sonar.password properties are required to run an analysis on this project. These properties have to be set to the credentials of a user having the User role on this project. You can set them either:
Since SonarQube 3.3, it is possible to run an analysis on a multi-module project whose modules contains source code from different languages.
In addition to the multi-module configuration, the only mandatory property to set is the language for each module: