I sent a support request on 11/20 for my three open source projects (libjpeg-turbo, VirtualGL, and TurboVNC) to be considered for a Travis CI open source plan. Travis CI support replied with a list of criteria for consideration. I believe that all three projects meet those criteria, but I asked for clarification on one of the criteria and never received a follow-up reply.
libjpeg-turbo in particular is used by millions of people worldwide (and may even used by Travis CI, as a matter of fact-- it’s in every Linux distribution and open source web browser I know of.) libjpeg-turbo admittedly has rather complicated builds, which include regression testing, but since libjpeg-turbo is considered to be critical Internet infrastructure, it’s necessary to run those builds as soon as bug fixes (which are often security-related) are pushed. Unfortunately, Travis CI instituted the new credit system right as I was in the middle of a flurry of bug fixes leading up to the libjpeg-turbo 2.1 beta release, so the 10,000 free credits got used up automatically before I was even aware of the new limits. The project’s pace has slowed considerably since the beta release, but because the project’s Travis CI credits are used up, right now we can’t spin pre-release builds with critical post-beta security fixes. libjpeg-turbo is out of funding until probably next June, and I can’t personally afford to pay for more Travis CI credits. I understand your desire to avoid “abusive” uses of your system, but I hope you would agree that providing zero-day fixes for a JPEG codec that is used by millions of people, is an ISO standard reference implementation, and is provided free of charge is not abusive. I am happy to work with you to reduce the credit load of our builds, if you would provide some transparency into how credit usage is calculated.