Travis CI Builds have been temporarily disabled for public repositories due to a negative credit balance

Written by Claudio Kuenzler - 0 comments

Published on September 29th 2023 - Listed in Git Coding Cloud

As I was about to create a new version of check_es_system (a monitoring plugin for Elasticsearch), I found that Travis CI builds were not working anymore.

In the last year I spent quite some time adding automated builds in Travis and added them into the repository (as .travis.yml) - just to see now no builds have been running in the past 8 months!

Negative Credit Balance?

When looking at the repository through Travis CI, a red error message popped up at the top of the screen:

Builds have been temporarily disabled for public repositories due to a negative credit balance

Yes, Travis CI has moved away from a free to a paid plan service while ago. However for some low key repositories, such as my monitoring plugins, there are almost no builds to do and many of the initial 10'000 free credits are still available:

Log out of Travis, log back in

After having contacted support, I got a fairly quick response to simply log out of Travis CI, log back in and trigger a build. This should clear the error and automated builds should start again.

By doing that, it seems that new permissions are needed in order for Travis to integrate itself into the GitHub repositories:

After authorizing Travis CI on my GitHub account, I forced a new build by using More options -> Trigger build:

And indeed, a new build starts up:

Builds working again for Pull Requests

After triggering a manual build on the newly created branch for the PR (I mentioned at the top), the build "icon" can now also be seen next to the PR again:

Add a comment

Comments (newest first)

No comments yet.