1–10 of 193 posts
https://twitter.com/james_hilliard/status/133608177669184307...
Hello James,
Thanks for writing in.
At the moment, credit allocation for OSS projects is on hold as per directives from management. Sincere apologies please.
We will provide updates once we get additional approval from management.
Thanks for your patience
-- MK
Your Friends @Travis CI
Test and Deploy with Confidence.
Good thing I was an earlier GitHub Actions adopter because now I don’t have to do as much work.
As linked above, the idea of new leadership starving OSS and simply supporting existing enterprise contracts was talked about extensively in the acquisition announcement thread: https://news.ycombinator.com/item?id=18978251
Are they trying to kill the product as fast as possible? Because waiting for a first-party solution before kicking 99% of your users out is the perfect way to do it, short of simply deleting their accounts. Good thing I was an earlier GitHub Actions adopter because now I don’t have to do as much work.
And I think they're missing the gravity of the situation—there were (and are still) a _ton_ of OSS projects out there that are configured to use Travis CI for their testing and build pipelines, and it's not free to switch to something else (even though there are many adequate alternatives).
I wish there was another way, like providing a meager amount of build minutes, or just reducing the OSS builds to run on a few dozen servers, even if that means days-long build queues. That's better than just ending service abruptly like they did.
I wrote [1] about my own plans, but I know many devs (especially for tiny side projects) just don't have the time to update them to something else, and we're likely to see a number of smaller projects kind of fall into disrepair from this.
[1] https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricin...
As linked above, the idea of new leadership starving OSS and simply supporting existing enterprise contracts was talked about extensively in the acquisition announcement thread: https://news.ycombinator.com/item?id=18978251
Speaking from experience: they're not even managing to service paying customers well.
Their home page at travis-ci.com still says:
> Testing your open source projects is always 100% free!
> Seriously. Always. We like to think of it as our way of giving back to a community that gives us so much as well.
That is simply not what's going on. As far as anyone can tell, they are offering some OSS which meet specific criteria (including no company funds any part of it, including paying people to work on it(?!)) free minutes in fixed monthly allotments, which you have to keep asking for every month. And there are only so many total minutes they are willing to give out, which apparently have now been frozen.
How can they have written a letter only two weeks ago saying "Open source accounts, as always, will be completely free under travis-ci.com"? How can their home page still say "Testing your open source projects is always 100% free!"??
At this point, it is hard to explain it as anything other than intentional manipulative dishonesty.
I don't understand why they don't just say "Yes, we can no longer provide free open source accounts." They aren't actually fooling anyone, I mean people notice that they don't have free accounts anymore, right? It is a weird attempt at some kind of reality distortion.
I guess you could try replying: "Credit allocation"? I don't understand, Paul Gordon wrote on Nov 24 "Open source accounts, as always, will be completely free under travis-ci.com." Is this not true?
I'm kinda curious what they'd say, but I guess it's just torturing poor support staff whose jobs probably aren't going to last either.
Earlier quoted context omitted.
Speaking from experience: they're not even managing to service paying customers well.
That seems to stem from the fact they killed off pretty much the entire engineering team after the acquisition (judging by tweets I remember reading shortly afterwards).
Many people are saying to those of us who _haven't_, for one reason or another, gotten completely off of Travis CI, "the writing was on the wall" or "you can't expect free forever." And I think they're missing the gravity of the situation—there were (and are still) a _ton_ of OSS projects out there that are configured to use Travis CI for their testing and build pipelines, and it's not free to switch to something els…
The license terms changed and boom now you're out of service.
If such OSS projects were running on Gitlab (either gitlab.com or selfhosted) then any of the members could have donated spare computing resources by running a gitlab runner on their prem.
Many people have PCs running 24/7 and could spare a vm to lend to their favourite projects.