SonarQube Community Build 25.6.0.109173 released

SonarQube Server / Community Build Releases
1

Hi all,

Sonar is proud to announce the June release of the SonarQube Community Build 25.6.0.109173. This version includes an improved detection of secrets and other enhancements.

Details are in the Release Notes. You’ll find all fixed tickets in the full release notes. Please open new threads for any questions you have about these or other features.

As usual, download is available at SonarSource.com. Docker image are available on Docker Hub. You can find on Artifact Hub how to use the latest SonarQube Community Build with the official Helm chart.

Elena

1 Like
2

After upgrading to 25.6.0.109173 I get this error: (My formatting, for better readability)

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: 
  Error creating bean with name 'ClassRealm{cobertura}-org.sonar.plugins.cobertura.CoberturaSensor': 
  Unsatisfied dependency expressed through constructor parameter 2: 
  No qualifying bean of type 'org.sonar.api.config.Settings' available: 
  expected at least 1 bean which qualifies as autowire candidate. 
  Dependency annotations: {}

How can I fix this. Must I roll back?

3

I have upgraded our 2025.2 Developer SonarQube instance to 2025.3 and I am getting the same issue running analysis in an Azure DevOps pipeline

When we run the ‘SonarQube Run Code Analysis’ Azure DevOps task (Version 7.3.0) we get the same error as reported above

Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'org.sonar.api.config.Settings' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoMatchingBeanFound(DefaultListableBeanFactory.java:2207)

If I check the background tasks on the SonarQube instance the analysis appears to have completed successfully. So the issue appears to be communication back to the Azure DevOps pipeline

Our setup is using the SonarSource created Docker image 2025.3.0-developer which we host in Azure

Luckily we have a UAT/Test instance and a production instance, so I don’t need to immediately roll back, but I won’t be upgrading our production instance until this is resolved

Any suggestions? Is this a regression?

4

@Per_Agerbaek the community plugin you use (the one defining CoberturaSensor) is not compatible anymore with latest versions of SonarQube as we removed some deprecated APIs.
Please contact the maintainers of that project and in the meantime the only fix is to uninstall this plugin.

@rfennell Double check that you don’t use any community plugin that is not compatible with the latest versions of SonarQube.

2 Likes
5

Thanks for the pointer, you were correct I had one plug-in that did not support the updated API. Once delete the analysis completed successfully.

I now need to decide whether I need the plugin (fork it and fix it) or if I stop using it.

Thanks again

1 Like
6

In case anyone else had the same problem, my issue was with the community Powershell plugin

I have submitted a PR to the project repo that updates the SonarQube API used so it works with SonarQube 2025.3

2 Likes
7

sonar-ps-plugin Not working. I tried the version of the new PS plugin, have created jar file from fix applied branch . The plugin is loading into SonarQube and able to see powershell quality profile but it is not reporting any issues when scanning a PowerShell project.

8

Dear @rajesh_daddanala,

Please raise this issue with the maintainers of the sonar-ps-plugin as this is community-driven. Maybe, also discuss it also with @rfennell raising this as well and providing the pull request on the plug-in.

Cheers :wine_glass:

1 Like