on a very specific repository (quite large typescript/javascript repository) the migration to the V2 azure devops task generated a side effect. The pipeline run forever (until it timeouts) but in reality it is failing in 5 minutes. This behaviour is directly related to the update of the task of the SonarCloud extension of Azure DevOps.
Do you have SONAR_SCANNER_OPTS set in your build variables to provide more memory to the scanner? If so, in this new version, you’ll need to migrate to the SONAR_SCANNER_JAVA_OPTS variable.
setting this new environment variables solved the OOM error, thank you!!
Though we still see tons of this errors from the scanner. All of them seems be related to the scan of specific “tsconfig.json” files in server subdirectory of the project (it’s a quite large lerna monorepo)