Bitbucket sonarcloud killed

We are trying to run a sonarcloud check on a project on bitbucket. The could get it running (so it starts), but then it just fails, when analyzing the first file (T-SQL). Unfortunately we don’t see any hint regarding for it to fail. It just said that it is killed. Is it because of memory limits put on the bitbucket cloud setup? We have increased to 2048MB (otherwise we the default it wouldn’t start at all really).

  • ALM used: Bitbucket Cloud

  • CI system used: Bitbucket Cloud

  • Scanner command used when applicable

    • pipe: sonarsource/sonarcloud-scan:1.0.1
      EXTRA_ARGS: -Dsonar.tsql.file.suffixes=.sql -Dsonar.plsql.file.suffixes=.plsql
      DEBUG: “true”
  • Languages of the repository: C#, SQL (T-SQL)

  • Error observed

‘’‘11:59:00.962 DEBUG: ‘XXXX/src/XXXX.Infrastructure/Migrations/Script/20190722_XXXX.sql’ generated metadata with charset ‘UTF-16LE’
/usr/bin/ line 24: 12 Killed sonar-scanner "{ALL_ARGS[@]}" 2>&1 13 Done | tee "{SCANNER_REPORT}’’’

Hello @Andreas_Soehnlein,

I am currently not aware of any memory issue we have related to sonarcloud bitbucket scanner and/or our T-SQL analyzer.
To help determine what is causing the problem, could you please provide some additional information and answer the following questions:

  • Is the analysis always failing on the same file ?
  • If yes, is the analysis succeeding when excluding this file ?
  • Is the analysis failing only on bitbucket, or is it also failing when attempting to analyze the project locally ?
  • If the analysis fails only on a single file, would you be willing to share it privately in order to determine what could cause the issue ?


1 Like
/usr/bin/ line 24:    11 Killed                  sonar-scanner "${ALL_ARGS[@]}" 2>&1
        12 Done                    | tee "${SCANNER_REPORT}"
✖ SonarCloud analysis failed.

We are seeing this issue on a fresh sonarcloud setup with our PHP repository on Bitbucket.
Any ideas on what we need to adjust?