The root folder of the project to analyze can be set through the sonar.projectBaseDir property since SonarScanner 2.4.Ex: sonar-scanner ttings=./myproject.properties The property ttings can be used to specify the path to the project configuration file (this option is incompatible with the sonar.projectBaseDir property).Įx: sonar-scanner -Dsonar.projectKey=myproject -Dsonar.sources=src1 The properties can be specified directly through the command line. This folder must contain a sonar-project.properties file if sonar.projectKey is not specified on the command line.Īdditional analysis parameters can be defined in this project configuration file or through command-line parameters.

If the files to be analyzed are not in the directory where the analysis starts from, use the sonar.projectBaseDir property to move analysis to a different directory. This is configured in sonar-project.properties as follows: sonar.projectBaseDir=/home/ftpdrop/cobol/project1 analysis begins from jenkins/jobs/myjob/workspace but the files to be analyzed are in ftpdrop/cobol/project1.

Mount the cacerts file that you've prepared in your target container.Assuming your certificate file is named mycert.cer and it's in your current local directory:īash -c 'cd /tmp/certs & keytool -keystore cacerts -storepass changeit -noprompt -trustcacerts -importcert -alias mycert -file mycert.cer' Add your certificate to the exported cacerts file.entrypoint cat sonarsource/sonar-scanner-cli /opt/java/openjdk/lib/security/cacerts > cacerts Extract the cacerts file from OpenJDK from the sonarsource/sonar-scanner-cli image:ĭocker pull sonarsource/sonar-scanner-cli.If you need to configure a self-signed certificate for the scanner to communicate with your SonarQube instance, we recommend using the OpenJDK provided with the sonarsource/sonar-scanner-cli image.

Second Rounds On Me Obie Trice Zip