Travis CI is no longer providing CI minutes for open source projects

Post by wegs » Tue, Dec 08, 2020, 2:18 AM UTC

Uehreka wrote: post #35

jrochkind1 wrote: post #8

Only a few weeks ago they wrote a letter ( https://blog.travis-ci.com/oss-announcement ) that said "Open source accounts, as always, will be completely free under travis-ci.com." 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…

I wonder how many people start out making pledges like that because they wish other companies would and they want to be the change they wish to see in the world. And they don’t realize that taking investor money means you no longer have the power to keep your promises even if you want to because you’re promising with other people’s money.

Post by jfrunyon » Tue, Dec 08, 2020, 2:22 AM UTC

bamboleo wrote: post #3

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.

Post by aeyes » Tue, Dec 08, 2020, 2:29 AM UTC

mmis1000 wrote: post #36

kzrdude wrote: post #25

Earlier quoted context omitted.

What's the benefit of circleci? I'm looking into switching from travis-ci.org to github actions, so far.

Speed, their main selling point. The default config uses a 8 2 core + 7.5g memory runner and capable to build simple projects in literal one minutes(includes deploy) after you push even without cache. And it seems they maintain their own apt mirror or whatever, the package install speed looks unreasonably fast. But they currently only give 250 minute (default config) per week to free account now, probably due to the…

Post by chordalkeyboard » Tue, Dec 08, 2020, 2:47 AM UTC

wegs wrote: post #51

Uehreka wrote: post #35

Earlier quoted context omitted.

I wonder how many people start out making pledges like that because they wish other companies would and they want to be the change they wish to see in the world. And they don’t realize that taking investor money means you no longer have the power to keep your promises even if you want to because you’re promising with other people’s money.

Part of the reason to make promises is that they are legally enforceable: https://www.investopedia.com/terms/p/promissory_estoppel.asp When I started an organization which was taken over in a rather hostile way, I was very careful to make a bunch of legally-binding promises before the takeover happened, to help prevent it from becoming too evil.

Post by dessant » Tue, Dec 08, 2020, 2:58 AM UTC

jfrunyon wrote: post #52

dessant wrote: post #19

I've moved on back when Travis CI employees have started recommending to turn off secret filtering in Windows build logs as a workaround for a bug, then decided to turn the workaround into a fix, exposing secrets in the logs of all Windows builds. https://travis-ci.community/t/current-known-issues-please-re... https://github.com/travis-ci/travis-build/pull/1719

"Secret filtering" is buggy, broken, stupid, misleading, and just plain wrong anyway. 1) If you can cause it to be run on arbitrary code then you can cause it to reveal the secret. Even if the only output you see is a pass or fail. 2) If you can't cause it to be run on arbitrary code, then why do you need to see any output?