From 8997640ac9561e5093ba8b43ba7e7b9b14bc14b4 Mon Sep 17 00:00:00 2001 From: Maurice Date: Thu, 8 Oct 2026 10:16:33 +0200 Subject: [PATCH] ci(sonar): give the JS/TS analyser 8 GB on full scans Since the ORM migration the scan of every push to dev stops with "the Node.js process running out of memory (heap size limit 4288 MB)" and fails the job, while PR scans, which only analyse changed files, stay under it. The hosted runner has 16 GB. --- sonar-project.properties | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/sonar-project.properties b/sonar-project.properties index e81f2a23f..d3bc20bcd 100644 --- a/sonar-project.properties +++ b/sonar-project.properties @@ -59,6 +59,12 @@ sonar.coverage.exclusions=\ # Locale files are large near-identical literal objects — keep them out of duplication metrics sonar.cpd.exclusions=shared/src/i18n/** +# The full analysis of a push to dev outgrows the JS/TS analyser's default heap +# of about 4 GB since the ORM migration and stops with "Analysis of JS/TS files +# failed". PR scans stay below it because they only look at the changed files. +# The hosted runner has 16 GB. +sonar.javascript.node.maxspace=8192 + # Only categorical, path-wide suppressions live here — cases where the rule can # never meaningfully apply to anything in the path. Instance-specific findings