SonarCloud analysis on master branch results in broken builds on all other PRs on GitHub

SonarQube Cloud
1

I integrated SonarCloud into Apache Creadur RAT with a separate GHA YML:

Analysis runs well on master branch, but all PRs run into broken builds, e.g.

The error log indicates an error within the SonarQube analysis:

[INFO] Load project branches
[INFO] Load project branches (done) | time=286ms
[INFO] Load project settings for component key: 'apache_creadur-rat'
[INFO] Load project settings for component key: 'apache_creadur-rat' (done) | time=237ms

Error:  Error during SonarScanner Engine execution

org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@1e4bccdf-org.sonar.scanner.scan.ModuleIndexer': Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@1e4bccdf-org.sonar.scanner.scan.filesystem.InputComponentStore': Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name 'BranchConfiguration' defined in org.sonar.scanner.scan.branch.BranchConfigurationProvider: Unsatisfied dependency expressed through method 'provide' parameter 0: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@1e4bccdf-com.sonarsource.branch.BranchConfigurationLoaderImpl': Unsatisfied dependency expressed through constructor parameter 1: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@1e4bccdf-com.sonarsource.branch.PrBranchConfigurationBuilder': Unsatisfied dependency expressed through constructor parameter 3: Error creating bean with name 'ProjectBindingFlag' defined in org.sonar.scanner.scan.branch.ProjectBindingFlagProvider: Unsatisfied dependency expressed through method 'provide' parameter 1: Error creating bean with name 'ProjectConfiguration' defined in org.sonar.scanner.scan.ProjectConfigurationProvider: Unsatisfied dependency expressed through method 'provide' parameter 5: Error creating bean with name 'FeatureFlagSettings' defined in org.sonar.scanner.featureflag.FeatureFlagSettingsProvider: Unsatisfied dependency expressed through method 'provide' parameter 0: Error creating bean with name 'FeatureFlags' defined in org.sonar.scanner.featureflag.FeatureFlagSettingsProvider: Failed to instantiate [org.sonar.scanner.extension.api.FeatureFlags]: Factory method 'provide' threw exception with message: Cannot invoke "java.util.Map.entrySet()" because "<parameter1>" is null
	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:804)
	at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:240)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1395)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1232)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:569)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:529)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:339)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:373)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:337)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.instantiateSingleton(DefaultListableBeanFactory.java:1221)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingleton(DefaultListableBeanFactory.java:1187)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:1123)
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:987)
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:627)
	at org.sonar.core.platform.SpringComponentContainer.startComponents(SpringComponentContainer.java:209)
	at org.sonar.core.platform.SpringComponentContainer.execute(SpringComponentContainer.java:189)
	at org.sonar.scanner.bootstrap.SpringGlobalContainer.doAfterStart(SpringGlobalContainer.java:146)
	at org.sonar.core.platform.SpringComponentContainer.startComponents(SpringComponentContainer.java:210)
	at org.sonar.core.platform.SpringComponentContainer.execute(SpringComponentContainer.java:189)
	at org.sonar.scanner.bootstrap.ScannerMain.runScannerEngine(ScannerMain.java:143)
	at org.sonar.scanner.bootstrap.ScannerMain.run(ScannerMain.java:58)
	at org.sonar.scanner.bootstrap.ScannerMain.main(ScannerMain.java:42)

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@1e4bccdf-org.sonar.scanner.scan.filesystem.InputComponentStore': Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name 'BranchConfiguration' defined in org.sonar.scanner.scan.branch.BranchConfigurationProvider: Unsatisfied dependency expressed through method 'provide' parameter 0: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@1e4bccdf-com.sonarsource.branch.BranchConfigurationLoaderImpl': Unsatisfied dependency expressed through constructor parameter 1: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@1e4bccdf-com.sonarsource.branch.PrBranchConfigurationBuilder': Unsatisfied dependency expressed through constructor parameter 3: Error creating bean with name 'ProjectBindingFlag' defined in org.sonar.scanner.scan.branch.ProjectBindingFlagProvider: Unsatisfied dependency expressed through method 'provide' parameter 1: Error creating bean with name 'ProjectConfiguration' defined in org.sonar.scanner.scan.ProjectConfigurationProvider: Unsatisfied dependency expressed through method 'provide' parameter 5: Error creating bean with name 'FeatureFlagSettings' defined in org.sonar.scanner.featureflag.FeatureFlagSettingsProvider: Unsatisfied dependency expressed through method 'provide' parameter 0: Error creating bean with name 'FeatureFlags' defined in org.sonar.scanner.featureflag.FeatureFlagSettingsProvider: Failed to instantiate [org.sonar.scanner.extension.api.FeatureFlags]: Factory method 'provide' threw exception with message: Cannot invoke "java.util.Map.entrySet()" because "<parameter1>" is null
	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:804)
	at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:240)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1395)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1232)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:569)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:529)
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:339)
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:373)
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:337)
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
	at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(DependencyDescriptor.java:254)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1760)
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1643)
	at org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:913)
	at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:791)
	... 22 common frames omitted

Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'BranchConfiguration' defined in org.sonar.scanner.scan.branch.BranchConfigurationProvider: Unsatisfied dependency expressed through method 'provide' parameter 0: Error creating bean with name 'jdk.internal.loader.ClassLoaders$AppClassLoader@1e4bccdf-

Is this an application error on the side of SonarQube or is something wrong with my configuration?

Thanks

1 Like
2

Hi,

Welcome to the community and thanks for this report!

Given how much is already going on in your log, I hesitate to ask this, but could you add -X to your Maven command so we get debug logging, try again, and post a pointer to new new log?

 
Thx,
Ann

4

Thanks for reaching out - I’ve added the “-X -e” parameters to the Maven call.

Existing PRs such as WIP: RAT-530: Prepare for a 0.18 release by ottlinger · Pull Request #601 · apache/creadur-rat · GitHub became green after a rebase.

I’m waiting for a freshly created branch (e.g. dependabot) ….

not sure if this problem related to the general GitHubAction problems of 2026-01-07, but will keep you updated.

Cheers

1 Like
5

Hi,

after adding “-X -e” to the command line call the log output is cut on GitHubActions so that I can only see the first 50 lines ….. thus I’m unable to see any stacktraces/more error messages.

e.g. Fix typo · apache/creadur-rat@55ee4e3 · GitHub

Above stacktrace indicates something within the Sonar-application so my hope was that someone can trace it back within your own code.

Thanks

6

Hi,

Hah! It did that to me at first too. I went to other windows to investigate possible causes and when I came back, the rest of the log started loading. All 128,834 lines… before the truncation :sweat_smile: Fortunately, it’s aaall there in the raw version of the log.

And this looks like an analysis of master?

2026-01-09T09:10:13.8740861Z [INFO] Auto-configuring branch master

That ended successfully?

2026-01-09T09:11:08.6769341Z [INFO] ANALYSIS SUCCESSFUL, you can find the results at: https://sonarcloud.io/dashboard?id=apache_creadur-rat&branch=master

For reference, here’s my somewhat-cleaned-up copy of the log.
log.log (5.3 MB)

 
Ann

8

The situation is still the same - freshly created PRs fail the SonarCloud build:

Unfortunately my Chrome does not load the log, so I only see the first couple of lines.

Can you see more of the errror message?
Thx

9

Hi,

Here’s the root:

What DevOps platform are we dealing with here? It’s likely that the PAT you’ve set at the project level has expired. It’s used only in a PR context, which would explain why only PRs fail.

 
Ann

10

SONAR_TOKEN is passed as a project secret via GitHub. As the builds are working properly on branch master I suspected it is a problem within the GitHubAction script I linked above.

The script is taken from the sonarcloud documentation ….. HTH

11

I tried finding the root cause again. As the analysis on branch master runs throught successfully with the same script I’m unsure if the error message is the correct cause:

2026-01-16T00:36:43.6383210Z Caused by: org.sonar.api.utils.MessageException: Project not found. Please check the 'sonar.projectKey' and 'sonar.organization' properties, the 'SONAR_TOKEN' environment variable, or contact the project administrator to check the permissions of the user the token belongs to

The projectKey and organisation values are passed in as parameters and the same SONAR_TOKEN is used that was issued quite recently. Any more hints where to look at?

Update: As the analysis from branch master seems to be updated I assume organization and projectId are correct:

Thanks again