We are using sonarcloud and we have 79k LOC divided in 6 projects where each project has 4 long lived branches (master, staging, qa, develop) and is currently supporting PR analysis.
Last week we sent a PR on a brand new project that has 2.1k LOC (included in the 79k) and we started getting this error…
This analysis will make your organization 'XYZ' to reach the maximum allowed lines limit (having 161226 lines). Please contact the administrator of the organization to resolve this issue.
and when we re-run the same pipeline we are getting…
This analysis will make your organization 'XYZ' to reach the maximum allowed lines limit (having 182398 lines). Please contact the administrator of the organization to resolve this issue.
there is clearly something wrong here, by just re running the pipeline I see +21k LOCs in a project that only has 2.1k LOCs? and is worth to mention that there is no new code, we are just adding a long lived branch.
Something is not right or I’m not understanding this… can anyone provide any help or guidance? this is the first time I see this problem, it’s also my first time using the cloud version, not sure if it was a wise choice
definitions: caches: sonar: ~/.sonar/cache # Caching SonarCloud artifacts will speed up your build steps: - step: &build-test-custom-sonar name: Build, test and analyze on SonarCloud (Custom run) caches: - node - sonar script: - npm install --quiet --legacy-peer-deps - npm run coverage -- --no-watch --no-progress --browsers=ChromeHeadlessNoSandbox - npm run sonar pipelines: default: - step: *build-test-custom-sonar
- ALM used (Bitbucket Cloud)
- CI system used (Bitbucket Cloud)
- Monorepo Project - Angular (JS/TS)