SonarCloud scans are not running

Template for a good new topic, formatted with Markdown:

  • ALM used Bitbucket Cloud
  • CI system used Bitbucket Cloud
  • Scanner command used when applicable (private details masked)
  • Languages of the repository - Java
  • Only if the SonarCloud project is public, the URL
    • And if you need help with pull request decoration, then the URL to the PR too
  • Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
  • Steps to reproduce
  • Potential workaround

The screen shot is the issue we are seeing.

We’ve upgraded Java to version: 1.4.0

Maven: maven:3.6.3-jdk-11

sonar.java.libraries’ property is empty (where is this file? In the WebUI sonarcloud.io?)

Are there docs on how to configure the data dictionary and where would that happen (where in the SonarCloud config? WebUI??)?

Here is some config file I was able to obtain:
organization=
projectKey=
serverUrl=https://sonarcloud.io
serverVersion=8.0.0.47729
branch=release/Release23R4
dashboardUrl=https://sonarcloud.io/

Hi,

Welcome to the community!

Your title says analysis isn’t running, but the fact that you have warnings indicates that it did run, just… with warnings.

Surely that’s a typo?

Let’s back up: what’s your build technology for Java? If it’s Maven or Gradle, you should be analyzing with the relevant scanner & your libraries will be automatically provided to analysis from the build environment.

The warning provides a link. Did you consult it?

 
Ann

Thanks so much for your reply Ann! I’m new to SonarCloud. Here is more info about the issue…

Your title says analysis isn’t running, but the fact that you have warnings indicates that it did run, just… with warnings.

Surely that’s a typo?

It was a typo. We use Java 11. We use Maven 3.6.1

Let’s back up: what’s your build technology for Java? If it’s Maven or Gradle, you should be analyzing with the relevant scanner & your libraries will be automatically provided to analysis from the build environment.

Our build technology for Java is Maven.

The warning provides a link. Did you consult it?

Yes we have consulted that page. Here’s what it looks like in our config for the pl/sql setting:

Hi,

That’s fine. And you’ll need to upgrade to Java 17 for analysis very soon.

Java 11 is deprecated, and that’s why you’re seeing a warning.

Then you should be analyzing with Maven too: mvn sonar:sonar.

Then you know that you configure the data dictionary (if you choose to do so) by setting properties on the analysis side, right?

 
Ann