Live data from Hacker News

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

news.ycombinator.com

81–90 of 193 posts

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

#81
Apple, Microsoft, Google, Facebook, or whatever could have bought Travis in order to make it remain free. All these companies rely heavily on open source work thus open source project CI. None of them did. Well that's the result of all this.

People are now moving to github actions, which are fine, but for how long github actions are going to be free for OSS projects as well? One cannot expect all these freebees to last forever, that's why open source needs financing like any other software development.

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

#82
post #59

Earlier quoted context omitted.

"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?

Unexpected behavior caused by any bug could print the variable to the build log, there is no need for malicious code to end up with compromised secrets.

Malicious code could also print the ROT13, hex, base64, or even selectively fail tests so that every failure is a bit of entropy.

Filtering secrets from logs only protects accidentally dumping your environment to a log Because you left in an echo $SECRET. It doesn’t stop a determined attacker who can run arbitrary code.

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

#83
post #55

Earlier quoted context omitted.

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…

Free accounts on CircleCI only have access to 2 core runners and can't run multiple jobs in parallel. Most open source projects I have seen on Travis do matrix builds which will take much longer to finish due to this restriction. Edit: Looks like you get 4 concurrent jobs if you register as an open source project.

We pay for CircleCI at $WORK and it’s pretty good. You get up to 40x concurrency in the “Pro” plans and I’m sure you could work whatever you need into enterprise.

My biggest complaint has been it lacks an very useful built in ability that Travis had, which is automatically running your builds on the merge of your current branch and target branch. You can right a script to do it yourself, but there missing some environmental variables to do it easily (because the build can start before the target branch is known).

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

#84
Probably the volume of users in the free tier is too big so they need to reduce expenses. It might be like giving away free storage space, too. There may be 0.001% of users that have a crazy amount of usage compared to average. At least my OSS project got to have many free builds, props to Travis CI.

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

#85

Apple, Microsoft, Google, Facebook, or whatever could have bought Travis in order to make it remain free. All these companies rely heavily on open source work thus open source project CI. None of them did. Well that's the result of all this. People are now moving to github actions, which are fine, but for how long github actions are going to be free for OSS projects as well? One cannot expect all these freebees to la…

Microsoft bought GitHub and offers github actions. No need for them to also buy Travis. If Microsoft buying Travis would have "saved" it, then why are you worried about GitHub actions' future?

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

#86

Earlier quoted context omitted.

Are there GitHub CI integrations that offer payment integration, so that the submitter of the pull request can be charged for the costs of CI related to their pull request?

what kind of project would you use this in? I can see how this might combat a very specific type of abuse, but it seems like it'd be even more effective in deterring contributions entirely.

Any project where I as project operator cannot afford CI credits for the hundreds of pull requests people submit to me while presuming I can afford to provide them CI.

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

#88
If anyone's looking for something to use for personal projects I currently use wercker and it's really easy to use (specify docker box, run commands) and has a free tier (but it's owned by Oracle so I still worry in the back of my head that they'll fuck it up any day now).

There's also Github Actions and Bitbucket Pipelines which I think are very similar in style, and also have free tiers.

There's also the "Raspberry PI in a closet" option, which I might explore over the Christmas holidays.

Dockerhub being free is something else I can't see lasting forever, their bandwidth costs must be immense? Although maybe they make enough from enterprise contracts to make up for it?

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

#90

Earlier quoted context omitted.

"including no company funds any part of it, including paying people to work on it(?!)" JetBrains open source licenses have a similar restriction https://www.jetbrains.com/opensource/ > Your project is NOT sponsored by a commercial company or organization and does NOT have paid employees > Your project does NOT provide commercial services (such as consulting or training) around the software, and does NOT distribute pa…

I have worked on many many open source projects. I don't think I have ever worked on any where there wasn't a single person writing code while getting paid by their employer. Is that enough to disqualify you from JetBrains criteria, do you think? In email from travis support it was expressed as: > Project must not be sponsored by a commercial company or organization (monetary or with employees paid to work on the pro…

I agree. Any open source project that's reasonably widely used is going to have some team from some commercial company submit a PR to fix some issue they're having at some point.
Post reply on HN