Message-ID: <1887266332.16662.1406704272976.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_16661_2076042963.1406704272976" ------=_Part_16661_2076042963.1406704272976 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Any user who's granted Execute Analysis permission can run an analysis.
If the Anyone group is not granted Execute A=
nalysis permission or if the SonarQube instance is secured (the
eAuthentication property is set to
true), the credentials of a user having been granted Execut=
e Analysis permission have to be provided through the
sonar-runner -Dsonar.login=3DmyLogin -Dsonar.passwor=
Note that for a preview/increme= ntal analysis, the user also has to be granted the Browse = ;permission on the project to be analyzed.
If a project cannot be accessed anonymously, the
sonar.password properties =
are required to run an analysis on this project. These properties have to b=
e set to the credentials of a user having the User role =
on this project. You can set them either:
-Dsonar.login=3DmyLog= in -Dsonar.password=3DmyPassword
A project cannot be anonymously accessed when either:
sonar.forceAut= henticationproperty is set to
sonar.force= Authenticationproperty is set to
false&n= bsp;and the Anyone group has not been granted a User role on the project
There is no security restriction.