=-wrapper-output=./bw-outputsv6/ -Dsonar.sourceEncoding=UTF-8ġ5:44:24.850 INFO: Using build-wrapper output: /home/jenkins/workspace/Project/Sourcen/100_Arbeit/./bw-outputsv6/build-wrapper-dump.jsonġ5:44:24.850 INFO: Available processors: 1ġ5:44:24.850 INFO: Using 1 thread for analysis according to value of “” property.ġ5:44:24.850 DEBUG: Unpacking analyzer to: /home/jenkins/workspace/Project/Sourcen/100_Arbeit/.scannerwork/.sonartmp/743351237207951652ġ5:44:26.332 DEBUG: ‘main.cpp’ generated metadata with charset ‘windows-1252’ġ5:44:26.347 DEBUG: Not enough content in ‘main.cpp’ to have CPD blocks, it will not be part of the duplication detectionġ5:44:26.351 WARN: Metric ‘comment_lines_data’ is deprecated. Sonar-scanner -X =XXX -Dsonar.projectKey=YYY -Dsonar.language=cpp -Dsonar.sources=. In a another step we use the sonar scanner with the cfamily plugin to analyze our code. opt/sonar-build/build-wrapper-linux-x86-64 -out-dir bw-outputsv6 ninja Target_1 We use the build-wrapper to catch the information of the compiler.
Our C++ project is build with ninja and uses the arm compiler and it compiles successful. This container is running on a jenkins job in our CI/CD toolchain. The SonarQube Scanner runs inside a docker linux-container. We are using the following Sonarqube setup:
0 kommentar(er)
