Sonar analysis times out

[thomasjoseph99]

Sonar analysis is timing out while scanning NPM projects. The sonar-scanner was invoked both directly and also through npm run. Please see below.

• Directly ::

• sonar-scanner -Dsonar.host.url=$SONAR_URL -Dsonar.projectKey=$CI_PROJECT_NAME -Dsonar.sources=CI_PROJECT_DIR -Dsonar.analysis.mode=preview -Dsonar.issuesReport.console.enable=true -Dsonar.gitlab.user_token=$SONAR_TOKEN -Dsonar.gitlab.commit_sha=$CI_COMMIT_SHA -Dsonar.gitlab.ref_name=$CI_COMMIT_REF_NAME -Dsonar.gitlab.project_id=$CI_PROJECT_ID

• NPM run (after updating package.json appropriately, and listing all required params (same as above) in sonar-scanner.properties) ::

    - npm install sonar-scanner
    - cp -f sonar-scanner.properties $CI_PROJECT_DIR/node_modules/sonar-scanner/conf/sonar-scanner.properties
    - npm run sonar-scanner                     

In both cases, the sonar analysis was stuck at "Execute Project Builders" and eventually timed out INFO: Execute project builders

Version used SonarQube: 6.7 Plugin: 3.0.2

Can you please take a look at the issue. Should the SonarGitLab specific parameters passed be different in case of NPM?

[akumar760613]

The sonarscan in gitlab using "Sonar-Gitlab-Plugin" is being timeout and struck for hours, running maven project for code analysis.

Can you please look into this?

[oi-ss]

May sound weird, but force set the sonar.gitlab.url property to the appropriate value in either the Administration UI or the command, and it will work.