Agreed. Looking at the status page, it appears that, for the past two days, there has been a huge spike in the Linux job backlog. Whereas normally there are only a few hundred in the backlog, yesterday the backlog spiked at 10 thousand! And today it’s already up to 6500!
We are in the process of migrating workers from travis-ci.org to travis-ci.com in preparation to fully shut down .org (or rather, make it read-only) on December, 31st.
Unfortunately, this might happen as a result — if we see a job stuck in a queue for more than 16 hours, we will review this on a case by case basis and possibly cancel the job to ensure resources are not being reduced across the platform.
For many usages moving to travis-ci.com is not possible or beneficial:
the problem that @dfawley mentioned about permissions
travis-ci.com has big open issues with broken caches and a broken cache cleanup page (see other threads on this forum but we also experienced it ourselves), which needs manual and awkward steps to clear caches. Before I found this page we were at the point of considering to move some projects back from travis-ci.com to travis-ci.org for that reason alone
inconsistent communication about the overall migration to travis-ci.com and what to expect and when things happen (the email with the migration deadline announcement wasn’t send to everyone, so what does that mean?)
Altogether, for bigger open source projects (which admittedly should probably have been set up on paid plans or a different kind CI in the first place), the situation points rather to a move away from Travis altogether.
Currently, it’s unclear if OS projects are going to be supported in the same way as they used to, whether the situation is going to improve any time soon, or if Travis would like to cut back on OS project support (which would be fair enough, you don’t owe us anything). It would just be nice to know what to expect
Looking at the monthly stats (https://www.traviscistatus.com/#month), it seems in previous spikes the number of “Active Linux Builds for Open Source projects” rose to meet demand while now it is capped at 555.
Ah, incorrect wording, my bad! Indeed, instead of describing it as an experience (‘put a cap on the number of builds’) it is indeed closer to ‘You get 10k credits for free. In that time, builds go fast, until the credits run out’.