Flies analized not running

SonarQube
,
1

I used Bitbucket pipeline and Angular CLI
The pipeline not running the files for analized
And ‘docker’ exceeded memory limit.

WHAT AM I WRONG?
Thanks for your time

This is my bitbucket-pipelines.yml

# This is a sample build configuration for JavaScript.
# Check our guides at https://confluence.atlassian.com/x/14UWN for more examples.
# Only use spaces to indent your .yml configuration.
# -----
# You can specify a custom docker image from Docker Hub as your build environment.
# Added comment
image: node:10.15.3

commonStep: &commonStep
  - step: &build-test-sonarcloud
  name: Build, test and analyze on SonarCloud
  size: 2x
  caches:
    - node
    - sonar
  script:
    - >
      wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - && \
        sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' && \
        apt-get update && \
        apt-get install -y google-chrome-stable xvfb procps
    - npm update
    - npm install
    - npm run lint
    - npm run test
    - pipe: sonarsource/sonarcloud-scan:1.2.0
      variables:
        SONAR_TOKEN: ${SONAR_TOKEN}
clone:
  depth: full # SonarCloud scanner needs the full history to assign issues properly

definitions:
  caches:
sonar: ~/.sonar/cache # Caching SonarCloud artifacts will speed up your build

pipelines:
    default:
    - <<: *commonStep
branches:
development:
  - <<: *commonStep
  - step:
        name: Deploy Heroku App Dev
        deployment: Development
        script:
          - git config http.postBuffer 52*******
          - git filter-branch -- --all
          - git push         
https://heroku:$HEROKU_API_KEY@git.heroku.com/$HEROKU_APP_NAME.git                                         
HEAD:master --force
master:
  - <<: *commonStep
  - step:
        name: Deploy Heroku App Master
        deployment: Production
        script:
          - git config http.postBuffer 52******
          - git filter-branch -- --all
          - git push 
https://heroku:$HEROKU_API_KEY@git.heroku.com/$HEROKU_APP_NAME.git  
HEAD:master --force

SONAR-PROJECT.PROPERTIES

sonar.projectVersion=1.0.0
sonar.sources=src/app
sonar.exclusions=**/node_modules/**,**/*.spec.ts
sonar.tests=src
sonar.test.inclusions=**/*.spec.ts
#sonar.javascript.lcov.reportPaths=coverage/lcov.info
sonar.typescript.lcov.reportPaths=coverage/lcov/lcov.info
sonar.junit.reportsPath=build/test-results/test
sonar.coverage.jacoco.xmlReportPaths=build/reports/jacoco/test/jacocoTestReport.xml

#Configuracion de puertos
sonar.web.port=9123
sonar.search.port=0

RESPONSE

INFO: Deploying custom rules bundle jar:file:/root/.sonar/cache/f2d4f3985cfdc8a536978941e81bc342/sonar-securityjsfrontend-plugin.jar!/js-vulnerabilities-rules-1.0.0.tgz to /opt/atlassian/pipelines/agent/build/.scannerwork/.sonartmp/eslint-bridge-bundle/package/custom-rules4061494546146142609

INFO: Found 2 tsconfig.json file(s): [/opt/atlassian/pipelines/agent/build/tsconfig.json, /opt/atlassian/pipelines/agent/build/e2e/tsconfig.json]
INFO: 183 source files to be analyzed
INFO: Analyzing 183 files using tsconfig: /opt/atlassian/pipelines/agent/build/tsconfig.json
INFO: 0/183 files analyzed, current file: src/app/config/agm/agm.module.ts
INFO: 0/183 files analyzed, current file: src/app/config/agm/agm.module.ts
INFO: 0/183 files analyzed, current file: src/app/config/agm/agm.module.ts
INFO: 0/183 files analyzed, current file: src/app/config/agm/agm.module.ts
INFO: 0/183 files analyzed, current file: src/app/config/agm/agm.module.ts
INFO: 0/183 files analyzed, current file: src/app/config/agm/agm.module.ts
INFO: 0/183 files analyzed, current file: src/app/config/agm/agm.module.ts
INFO: 0/183 files analyzed, current file: src/app/config/agm/agm.module.ts
INFO: 0/183 files analyzed, current file: src/app/config/agm/agm.module.ts
INFO: 0/183 files analyzed, current file: src/app/config/agm/agm.module.ts
INFO: 0/183 files analyzed, current file: src/app/config/agm/agm.module.ts

2

Hi @josegironp, welcome to the SonarSource Community!

I think this point you mentioned is a sign of your general problem: lack of memory. If you’re scanning within Docker, you’ll need to make sure the container has enough resources (keep increasing til you see no sign of problem). And then also, within the container, you may also need to configure our scanner to give more memory to the node process we use during analysis. See our Troubleshooting section in the Typescript docs for more details.

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.