Background Task failed after Sonar-scanner analysis

[Colin]

Hey there.

@akash_p

INFO: Analysis report compressed in 89957ms, zip size=619.5 MB

Long story short, your analysis report is about 100MB too big (it can be, at maximum, 512 MB with a Postgres database).

I would refer to a post here where advice is given on shrinking the analysis report:

SonarQube + postgresql: invalid memory alloc request size

Hello Carlo, You can challenge the fact that the report is stored and/or that the supported size is limited to 1Gb on Postgres. However, in your position, I would first wonder whether it is any good to the performance of the analysis (during scanner run, network transfert, asynchronous processing, …) to have a 1Gb report produced in the first place. Sources are compressed in the report and analysis data is stored in a size optimized binary format (that roughly the content of the report). I’m…

Another option would be to split the scan into several projects, if there’s a logical way of splitting the sources (a monorepo, for example, with many different applications)