SonaQube is causing builds to fail

How can we resolve this issue, please? Our builds are failing, and we just got billed?

The job was not started because recent account payments have failed, or your spending limit needs to be increased. Please check the ‘Billing & plans’ section in your settings

What can we do?

1 Like

Hi,

Welcome to the community!

This error message doesn’t sound like it comes from us. If you still believe it does, we’ll need more detail to help you.

 
Ann

I get the same error:

SonarCloud - The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the ‘Billing & plans’ section in your settings.

I’ve checked and there are no problems with the payment, so I understand the problem is the total number of lines of code because I also have this message in my panel:

99.993k private lines of code analyzed within 1 projects of 100k
* Analyzed lines of code(99.993k)
* Available lines of code(7)

I’ve modified my sonar-project.properties to only scan a few files.

But it seems like SonarCloud calculates the total number of lines based on the last successful scan. Since the current scan fails before it even starts, SonarCloud still thinks we have 99.993 lines, so I can’t start a new analysis.

I’m stuck in a vicious cycle.

Any ideas on how to move forward?

Hi, check your github options for us the issue came because we selected github runner instead of our self hosted runner.

Regards

Tunde Famakinwa
Engineering Manager
08037075735

2 Likes

Hi @Appquestduke thanks for sharing the solution to your issue, we’ve added it to our docs as a troubleshooting note to help future users who run into this specific billing message.

Best,

Tony

2 Likes