Bitbucket Pipeline - Sonar 1.2.1 still getting Node 8 warnings

We’ve bumped to Sonarcloud 1.2.1 but are still getting warnings about Node v8. Any thoughts?

  • Bitbucket Cloud
  • Bitbucket Pipelines
  • Javascript/Typescript repo

The version of Node.js (v8.12.0) you have used to run this analysis is deprecated and we will stop accepting it from 16th November 2020. Please update to at least Node.js 10. Read more here

sonarcloud-scan: &sonarcloud-scan
      name: SonarCloud - Scan
  image: sonarsource/sonarcloud-scan:1.2.1
  artifacts:
    - sonarsource/sonarcloud-scan/sonarcloud-scan.log
  caches:
    - sonar

  script:
    - export DEBUG=$SONAR_SCAN_DEBUG
    - export SONAR_SCANNER_OPTS='-Xmx512m'
    - export EXTRA_ARGS='-Dproject.settings=sonar-project.properties -Dsonar.eslint.reportPaths=eslint-report.json'
    - mkdir -p ${BITBUCKET_CLONE_DIR}/sonarsource/sonarcloud-scan
    - export BITBUCKET_PIPE_STORAGE_DIR=${BITBUCKET_CLONE_DIR}/sonarsource/sonarcloud-scan
    - /usr/bin/run-scanner.sh

Hello @Zach_Goldberg,

Where are you still seeing this warning? We show this warning both in the SonarCloud UI and on PR decorations.

If you still have this warning on the SonarCloud UI it could mean that you haven’t analysed your default branch with your upgraded pipeline.
If that’s not the case could you please supply the ID of a background task for which you still get this warning? You can find this by navigation to your project on SonarCloud and selecting Administration > Background Tasks.

Hi Tom,

I believe we have merged into our default branch (develop) and are still seeing the warnings in the bitbucket UI. Here is a background task ID AXVql4Av1tBx5HJgUmY2

Thank you,
Zach