Noticed in https://github.com/dask/community/issues/107 this morning. Travis is putting much much stricter limits on free-tier use of its CI services.
https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
For those of you who have been building on public repositories (on travis-ci.com, with no paid subscription), we will upgrade you to our trial (free) plan with a 10K credit allotment (which allows around 1000 minutes in a Linux environment).
We will be offering an allotment of OSS minutes that will be reviewed and allocated on a case by case basis. Should you want to apply for these credits please open a request with Travis CI support stating that you鈥檇 like to be considered for the OSS allotment.
The blog post also makes it sound like macOS jobs will no longer be available for free-tier users, but honestly the blog post's discussion of that is very confusing.
I'm not sure yet what we should do with out existing Travis jobs, need to do some more research on how long they take to run and what that means in relation to these limits. :tired_face:
Thanks a lot for bringing this up @jameslamb !
Yeah, seems that macOS builds will be paid...
Also, please notice we use travis-ci.org, not .com. Looks like this also matters.
https://docs.travis-ci.com/user/billing-faq#what-if-i-am-building-open-source
Each of the Travis CI Plans can have an amount of special OSS credits per month assigned to run builds only on public repositories. To find out more about it please contact the Travis CI support team.
Very "informative"! 馃槂
Love for OSS has gone: https://github.com/travis-ci/travis-web/pull/2569/files
Also, please notice we use
travis-ci.org, not.com. Looks like this also matters.
OK, org will be archived 31st December: https://travis-ci.community/t/org-to-com-migration-deadline/10260.
Love for OSS has gone: https://github.com/travis-ci/travis-web/pull/2569/files
I found this thread while googling for more info about the "OSS only credits". That linked change is disheartening.
Looks like my own OSS project will need to discuss the pros and cons of switching over to GitHub Actions instead of migrating our travis-ci.org repos to travis-ci.com. If you go through the process of requesting OSS credits, I'd love to see the results here. It would help us with our own decision-making process!
Just got this error on a personal project of mine that runs on travis-ci.org
Builds have been temporarily disabled for public repositories due to a negative credit balance. Please go to the Plan page to replenish your credit balance or alter your Consume paid credits for OSS setting.

So, what's the plan?
Mark Travis CI as non-required for the transfer period. Transfer LightGBM project from org to com domain. Write a letter to Travis support team kindly asking them for open source project points. Choose the most basic (and free plan) with ideally unlimited runs/minutes (but probably with just 1 parallel job) for Linux and Windows. Spend all given tokens for macOS builds. Spend some time looking at our spendings. If everything is OK, set Travis CI required back.
Something like this, right?
Ok yes, I agree with this plan!
If you can do the org to com transfer, I can take responsibility for writing to Travis support. What do you think?
I'm not sure I have enough rights for migrating. Anyway, the first step is to mark Travis CI as non-required for PRs, because after migrating we will face runs cancelation as you've pointed in https://github.com/microsoft/LightGBM/issues/3519#issuecomment-723532090.
@guolinke Could you please help with marking Travis checks as non-required? Also, WDYT about this topic in general?
It's really unbelievable.
The official Travis documentation on migrating to .com STILL refers to .com as a beta!
https://docs.travis-ci.com/user/migrate/open-source-repository-migration

Two tasks just failed too even start on Travis. I'm hoping it's temporary and not sure if it's related to this issue, but want to note the links here in case we need to come back to them later.
https://travis-ci.org/github/microsoft/LightGBM/jobs/743842061
https://travis-ci.org/github/microsoft/LightGBM/jobs/743842062
An error occurred while generating the build script.
Most helpful comment
I found this thread while googling for more info about the "OSS only credits". That linked change is disheartening.
Looks like my own OSS project will need to discuss the pros and cons of switching over to GitHub Actions instead of migrating our travis-ci.org repos to travis-ci.com. If you go through the process of requesting OSS credits, I'd love to see the results here. It would help us with our own decision-making process!