Upgrading the SonarScan Java Version in my Node Project

Sonar Version: Version v3.23.0+2

How is SonarQube deployed?: Docker

I have a Concourse pipeline that runs a SonarQube Scan. Since the Sonar Scan uses Java, we need to make sure our Sonar Scan uses the appropriate version. I’m trying to update the Java version to 11 but the pipeline is still pointing to Java 1.8.

Here is my Sonar Properties file:


As you can see I changed the source from 1.8 to 11.

This change had no effect on the pipeline identifying the intended Java version.

Here is my sonar.yml file. I tried replacing the repository url with “java11” instead of “node”.

platform: linux
  type: docker-image
    repository: docker.artifactory.company.com/flow/java11
    tag: "latest"
    username: ((user))
    password: ((password))
  - name: code-repo
  - path: code-repo/server/node_modules
  dir: code-repo
  path: cicd/scripts/sonar.sh

This change just broke the pipeline step.

Finally here is my sonar.sh file.

set -e
npm install -g n
n 14.16.0
node -v
npm -v

cd server/
export token=$(command to get token)

echo "registry = npm registry url

npm ci
cd ..
flow sonar scan $ENVIRONMENT

Thank you in advance!Preformatted text


Welcome to the community!

Can you check your SonarQube page footer and share the SonarQube version?

This doesn’t impact the JVM version analysis is run with. By the time these properties are read, the JVM has already started. This property tells the analyzer that you’re writing Java 11.

What you need to do is make sure the correct version of Java is installed on your build agent, and that it’s used to fire the analysis job. I’m not familiar with Concourse, so I can’t give you the exact syntax to do that, though.


We are using Version 9.9 (build 65466)

1 Like

We ended up changing our sonar.sh file to this.

npm install 
export https_proxy=http://company-url.com:7070
set -e -x
flow sonar scan $ENVIRONMENT

This enabled the Sonar Scan step in our pipeline to pass but we received more errors.

We received thus error in the sonar dashboard.

“Javascript/Typescript/CSS rules were not executed. Error when running ‘node -v. Is Node.js available during analysis?”

I’m assuming this is because we took out the node logic from our sonar step.


Yes, analysis needs Node.js if you’ve got CSS, JavaScript or TypeScript in your project.


We finally found the issue. The Docker image which ran the step in our concourse pipeline was an older image. We updated to the newest Docker image to run node. This image also ran Java 11 behind the scenes.

1 Like