Skip to content

Plugin throws a 'org.sonar.api.config.Settings' type exception during analysis on SonarQube 2025.3 #37

@bm-fez

Description

@bm-fez

When I upgraded my 2025.2 Developer SonarQube instance to 2025.3 I got an error running analysis in an Azure DevOps pipeline.

When I ran the ‘SonarQube Run Code Analysis’ Azure DevOps task (Version 7.3.0) it failed with the error

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)

After a chat on the SonarQube forum I was able to confirm the issue was this plugin. Once it was deleted analysis complete, but obviously with the PowerShell analysis steps.

So my assumption is that this plugin needs to be updated to reflect the changed API calls between SonarQube 2025.2 and 2025.3

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions