How to find out why Travis is not running?

Builds had suddenly stopped for Travis CI - Test and Deploy with Confidence.

Here is a new PR .travis.yml: Run `pytest` in verbose mode to debug freeze by abitrolly · Pull Request #50 · jonmatthis/freemocap that doesn’t even appear in the list of PRs.

As an external contributor, how can I know the reason?

  • problem with Travis itself (but if green)
  • Travis had been turned off for the project by project admins
  • project run over OSS quota

Doing some looking on the backend and querying, the event request in question, in this case a pull request, was rejected via:

jonmatthis does not have enough credits.

Good to know, but…

Is asking here is the only way?

Hey @abitrolly,

If the end user is using OSS, they only get 10,000 build credits - which means, the user will run into this, where the event request will be rejected and then on occasion will look at their OSS credits and see they’ve used the 10,000 allotment. This is in the plans/pricing area, and looks like this:

If the user is building open source and happen to spill over the OSS allotment, have the user email the Travis CI Support Team. With info about their VCS, and how many credits (build minutes) they would like to request (should they run out of credits again you can repeat the process to request more or to discuss a renewable amount).

If it’s a problem with Travis, like you said, you can find this out via:

If they are apart of an organization, the admins on the account receive email notifications about going over the OSS allotment.

This still doesn’t answer the question.

Which is now the question.

I’ll retype what I typed in my original answer, maybe you missed the snippet about how the admins receive notifications about their OSS allotments going over.

(There’s also a huge banner that invokes this message if 10,000 credits are used in an OSS project).

As an external contributor you probably can make a good assumption given context clues, one of the clues you gave out is “The builds stopped suddenly”. That at least told me without even having to check (although I did) it was most likely a credit issue, another example is, if there’s a working .travis.yml, and it’s a OSS project and nothing is firing, there’s a good chance it reverts back to a credit issue.

Asking here is not the only way, the most obvious and logical other way is you could ask the repository owner, see if they have ran out of credits or disabled Travis on their repo. There’s also

1 Like