- ALM used: Bitbucket
- CI system used: Jenkins / Docker / Podman
- Scanner command used when applicable: see below
- Languages of the repository: Java + multiple others
- SonarCloud project is public: no
- Error observed: no error
- Potential workaround: n/a
We run our Sonar Analysis in a containerized CLI (using SonarCloud), when looking at the logs, I see:
and outdated version (8.0.0.52441
) of SonarCube (not SonarCloud) mentioned. The results actually end up in SonarCloud.
podman -r run -t --rm \
-v /MYCODE:/usr/src \
-w /usr/src/ \
-e SONAR_HOST_URL=http://sonarcloud.io \
-e SONAR_TOKEN=**** \
-e SONAR_SCANNER_OPTS=OURSCANNEROPTIONS \
sonarsource/sonar-scanner-cli:5
Partial logs
...
INFO: Scanner configuration file: /opt/sonar-scanner/conf/sonar-scanner.properties
INFO: Project root configuration file: /usr/src/sonar-project.properties
INFO: SonarScanner 5.0.1.3006
INFO: Java 17.0.8 Alpine (64-bit)
INFO: Linux 4.18.0-477.27.1.el8_8.x86_64 amd64
INFO: SONAR_SCANNER_OPTS= -Dsonar.branch.name=develop -Dsonar.branch.target=master -Dsonar.newCode.referenceBranch=master -Dsonar.organization=OURORG -Dsonar.projectKey=OURPOROJECT -Dsonar.java.binaries=target -Dsonar.java.libraries=**/*.jar -Dsonar.coverage.jacoco.xmlReportPaths=**/jacoco.xml -Dsonar.qualitygate.wait=true
INFO: User cache: /opt/sonar-scanner/.sonar/cache
INFO: Analyzing on SonarQube server 8.0.0.52441
...
I would expect SonarCloud to internally run on something newer,