Hi Encarna,
If you simply try to update your scanner version (1) as you did, what do you get?
- pipe: sonarsource/sonarcloud-scan:2.0.0
If this leads to an OOM issue, could you try to add this option to raise the amount of RAM available for the Node.js process in the analyzer (2), as it was proposed in this thread:
- pipe: sonarsource/sonarcloud-scan:2.0.0
variables:
EXTRA_ARGS: '-Dsonar.javascript.node.maxspace=4096'
If the issue persists, could you join your log files here?
I tried the above and it causes other issues because then , we bypass the sonar properties that we have in pom.xml , which we pass with command mvn -B sonar:sonar -Dsonar…
You mean that trying (1) led to some issues with your Maven scan job?
If we adopt - pipe: sonarsource/sonarcloud-scan:2.0.0, can we pass the sonar properties using a property file such as .sonarcloud.properties? Is this the file name that we need to use ?
You can pass them in EXTRA_ARGS as shown in (2). Would that fit?