Increase the memory via the SONAR_SCANNER_OPTS environment variable when running the scanner from a zip file: export SONAR_SCANNER_OPTS="-Xmx512m" Then, assuming both the cacerts and Dockerfile are in the current directory, create the new image with a command such as: docker build -tag our-custom/sonar-scanner-cli. Create a Dockerfile with the following contents: FROM sonarsource/sonar-scanner-cliĬOPY cacerts /usr/lib/jvm/default-jvm/jre/lib/security/cacerts e SONAR_SCANNER_OPTS="-Dsonar.projectKey=$:/opt/sonar-scanner/.sonar/cache \Īlternatively, you can create your own container that includes the modified cacerts file. To scan using the SonarScanner Docker image, use the following command: docker run \ Running SonarScanner from the Docker image
Run the following command from the project base directory to launch analysis and pass your authentication token: sonar-scanner -Dsonar.login=myAuthenticationToken.If you need more debug information, you can add one of the following to your command line: -X, -verbose, or -Dsonar.verbose=true. You should get output like this: usage: sonar-scanner Verify your installation by opening a new shell and executing the command sonar-scanner -h ( sonar-scanner.bat -h on Windows). Add the $install_directory/bin directory to your path.Update the global settings to point to your SonarQube server by editing $install_directory/conf/sonar-scanner.properties: #- Default SonarQube server We'll refer to it as $install_directory in the next steps. Expand the downloaded file into the directory of your choice.To run SonarScanner from the zip file, follow these steps: # Path is relative to the sonar-project.properties file. Configuring your projectĬreate a configuration file in your project's root directory called sonar-project.properties # must be unique in a given SonarQube instance The SonarScanner is the scanner to use when there is no specific scanner for your build system.
0 kommentar(er)
