We are trying out the SonarCloud offering via a bitbucket pipeline.
The sanner starts and sensors identify code…(this is a mixed PHP and Javascript repository). The first file to be flagged for analysis is a 302 byte javascript file. But it just keeps repeating that analysis
…
INFO: No report imported, no coverage information will be imported by JaCoCo XML Report Importer
INFO: Sensor JaCoCo XML Report Importer [jacoco] (done) | time=15ms
INFO: Sensor JavaScript analysis [javascript]
INFO: 263 source files to be analyzed
INFO: 1/263 file analyzed, current file: /opt/atlassian/pipelines/agent/build/…
INFO: 1/263 file analyzed, current file: /opt/atlassian/pipelines/agent/build/…
INFO: 1/263 file analyzed, current file: /opt/atlassian/pipelines/agent/build/…
INFO: 1/263 file analyzed, current file: /opt/atlassian/pipelines/agent/build/…
…
Each analysis iteration is about 10 seconds. Based on some other posts, I have tried setting the variable SONAR_SCANNER_OPTS: -Xmx4098m for the pipe in bitbucket-pipelines.yml. That seems to have no effect.
I have not been able to get a clue what is happening, even with debug enabled.
Any thoughts?