Analysis not working due to node version issue

Hello everyone,

We’ve setup Bitbucket Pipelines to trigger code analysis and quality gate reviews on each pull request change with the following versions of sonarcloud packages:

  • sonarsource/sonarcloud-scan:1.2.0
  • sonarsource/sonarcloud-quality-gate:0.1.3

But since May we’ve seen less Sonar hints in our pull requests, and after investigations it seems that the code analysis was not running, but the pipeline was marked as Success.

In the code analysis step (sonarcloud-scan) there was this log message:
ERROR: Only Node.js v12.22 or later is supported, got 12.18.3.

Does anybody faced this issue ? Because for mostly 3 months we didn’t noticed that and as code analysis were not correctly done, a lot of “bad” code could have been pushed.

The solution was to upgrade to the latest version of these two packages, but I don’t understand why I didn’t received any communication about that and why those previous versions stopped running as usual.

Kind regards,

Hi Ismail,

Welcome to the Community! Thank you for bringing this up.

We will look into what is happening with Bitbucket pipelines. I have created an internal insight to follow this subject. c.c. @Martin_Bednorz and @Christophe_Havard.

I’m very sorry that you went through this experience.

We had to upgrade to v12.22 internally and we failed to communicate this enough.

In general, we encourage using the latest Node LTS version and we do not officially support Node versions outside of LTS, even if they might work. There are two LTS versions, v14 and v16. Node v12 ended life last April.

If you could help me understand your situation better:

  • Is there any reason you don’t use the latest Node LTS version?
  • Did you see any deprecation warnings in Bitbucket or SonarCloud?
  • Do you follow Community announcements or SonarCloud’s “What’s new”?
  • What would be your preferred way for us to reach out to you?

Kind regards,


I’m facing an identical issue from BitBucket

    - step: &sonar-analyze
        name: Analyze with SonarCloud
        image: circleci/node:14.18.2-browsers
        size: 2x # Total memory is 8GB
          - node
          - pipe: sonarsource/sonarcloud-scan:1.2.2

This yields

INFO: Sensor JavaScript analysis [javascript]
INFO: Deploying custom rules bundle jar:file:/root/.sonar/cache/ce591e3f7610860294db52053899e90f/sonar-securityjsfrontend-plugin.jar!/js-vulnerabilities-rules-1.0.0.tgz to /opt/atlassian/pipelines/agent/build/.scannerwork/.sonartmp/eslint-bridge-bundle/package/custom-rules17248008608657546274
ERROR: Only Node.js v12.22 or later is supported, got 12.18.3.
org.sonarsource.nodejs.NodeCommandException: Only Node.js v12.22 or later is supported, got 12.18.3.
	at org.sonarsource.nodejs.NodeCommandBuilderImpl.checkNodeCompatibility(
	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.initNodeCommand(
	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.startServer(
	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.startServerLazily(
	at org.sonar.plugins.javascript.eslint.AbstractEslintSensor.execute(
	at org.sonar.scanner.sensor.AbstractSensorWrapper.analyse(
	at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(
	at org.sonar.scanner.sensor.ModuleSensorsExecutor.lambda$execute$1(
	at org.sonar.scanner.sensor.ModuleSensorsExecutor.withModuleStrategy(
	at org.sonar.scanner.sensor.ModuleSensorsExecutor.execute(
	at org.sonar.scanner.scan.ModuleScanContainer.doAfterStart(
	at org.sonar.core.platform.ComponentContainer.startComponents(
	at org.sonar.core.platform.ComponentContainer.execute(
	at org.sonar.scanner.scan.ProjectScanContainer.scan(
	at org.sonar.scanner.scan.ProjectScanContainer.scanRecursively(
	at org.sonar.scanner.scan.ProjectScanContainer.doAfterStart(
	at org.sonar.core.platform.ComponentContainer.startComponents(
	at org.sonar.core.platform.ComponentContainer.execute(
	at org.sonar.scanner.bootstrap.GlobalContainer.doAfterStart(
	at org.sonar.core.platform.ComponentContainer.startComponents(
	at org.sonar.core.platform.ComponentContainer.execute(
	at org.sonar.batch.bootstrapper.Batch.doExecute(
	at org.sonar.batch.bootstrapper.Batch.execute(
	at org.sonarsource.scanner.api.internal.batch.BatchIsolatedLauncher.execute(
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.base/java.lang.reflect.Method.invoke(
	at org.sonarsource.scanner.api.internal.IsolatedLauncherProxy.invoke(
	at com.sun.proxy.$Proxy0.execute(Unknown Source)
	at org.sonarsource.scanner.api.EmbeddedScanner.doExecute(
	at org.sonarsource.scanner.api.EmbeddedScanner.execute(
	at org.sonarsource.scanner.cli.Main.execute(
	at org.sonarsource.scanner.cli.Main.execute(
	at org.sonarsource.scanner.cli.Main.main(

A breaking change like this should have been applied to a new version of sonarsource/sonarcloud-scan:1.2.2

Also, this does not appear to fail the build step in BitBucket…how/why would it not? Then, when the quality gate check is made it passes as well with seemingly a default passing score.

I was able to remedy my situation by switching to 1.4.0 of this pipe

1 Like