Urgent: Unexpected NoClassDefFoundError Impacting Multiple Builds - Need Assistance

SonarQube Cloud
1

We’ve been experiencing an unusual issue for the last few hours that is affecting multiple separate build processes in our CI/CD pipeline. The issue manifests as a java.lang.NoClassDefFoundError specifically related to LicensedPluginRegistration, causing our builds to fail during the SonarCloud scan step.

Here’s the error log for reference:

##[error]ERROR: Error during SonarScanner execution
java.lang.NoClassDefFoundError: com/sonarsource/plugins/license/api/LicensedPluginRegistration
ERROR: Error during SonarScanner execution
java.lang.NoClassDefFoundError: com/sonarsource/plugins/license/api/LicensedPluginRegistration
##[error]at com.sonar.cpp.plugin.CFamilyPlugin.define(CFamilyPlugin.java:31)
	at org.sonar.scanner.bootstrap.ExtensionInstaller.installExtensionsForPlugins(ExtensionInstaller.java:51)
	at org.sonar.scanner.scan.ProjectScanContainer.installPluginsForLanguages(ProjectScanContainer.java:69)
	at org.sonar.scanner.scan.ProjectScanContainer.doBeforeStart(ProjectScanContainer.java:57)
	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:121)
	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)
	at com.sonar.cpp.plugin.CFamilyPlugin.define(CFamilyPlugin.java:31)
	at org.sonar.scanner.bootstrap.ExtensionInstaller.installExtensionsForPlugins(ExtensionInstaller.java:51)
	at org.sonar.scanner.scan.ProjectScanContainer.installPluginsForLanguages(ProjectScanContainer.java:69)
	at org.sonar.scanner.scan.ProjectScanContainer.doBeforeStart(ProjectScanContainer.java:57)
	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:121)
	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)
##[error]at org.sonar.scanner.bootstrap.ScannerContainer.doAfterStart(ScannerContainer.java:396)
	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:123)
	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)
	at org.sonar.scanner.bootstrap.GlobalContainer.doAfterStart(GlobalContainer.java:128)
	at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:123)
	at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:109)
	at org.sonar.batch.bootstrapper.Batch.doExecute(Batch.java:57)

Context:

  • Timing: The issue started occurring a few hours ago and is consistently replicating across different build jobs.
  • Token: Our Personal Access Token (PAT) is valid and hasn’t expired.
  • Licensing: We have verified our licensing details on the SonarCloud dashboard, and everything appears to be in order.

What We Have Checked:

  1. PAT Validation: Reconfirmed that the Personal Access Token used for authenticating to SonarCloud is still valid.
  2. License Verification: Checked our SonarCloud account’s billing and subscription status, which are active and up-to-date.
  3. Impact Scope: This issue is not isolated to a single build or project but is affecting multiple builds.

Queries:

  1. Has anyone else been experiencing a similar issue?
  2. Is this possibly related to any recent updates or maintenance activities on the SonarCloud platform?
  3. What steps can we take to debug this issue further given that we’re using SonarCloud as a SaaS, and thus, have limited access to server-side configurations?

We appreciate any urgent assistance on this matter as it’s critically affecting our build processes. Thank you in advance for your time and support.

2

Hey there.

Thanks for the report. I’ve sounded the alarm internally since today there was an upgrade of the CFamily analyzer. Stay tuned and thanks for your patience.

3

Thanks Colin, appreciate the prompt reply.

4

Hey @RHCertara

We toggled something in the backend. Can you see if the issue persists?

5

Sure, we are just re-running the pipeline.

1 Like
6

That looks to have resolved our issue. Great work, thanks.

2 Likes
7

Thanks. The issue is mitigated, but not solved yet. :pray: Thank you very much for the report.

1 Like
10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.