11–20 of 193 posts
It's a shame. Something like this should exist, but I can't blame them for not wanting to do it for free.
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…
Since then I have switched a bunch of projects over to Github Actions, fortunately they were all relatively simple enough to make that straightforward.
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…
I honestly think this is the price that people pay for using proprietary software. 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 proj…
The magic of Travis was that with a couple clicks of OAuth you were signed up and running builds for your own PRs. My first thought upon seeing this years ago was “How many people are using this to mine crypto?!“.
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…
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 paid versions of the software
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 think it is more likely that there is intense internal conflict around this decision, and some people may be openly reaffirming their beliefs in the mission of TravisCI.
With Github Actions on the scene now, I don't see much reason to use Travis over one of the alternatives.
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…
Earlier quoted context omitted.
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).
I will never again doubt what "purchase by private equity" means again, it is clear.
https://travis-ci.community/t/current-known-issues-please-re...
Earlier quoted context omitted.
I honestly think this is the price that people pay for using proprietary software. 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 proj…
Running arbitrary code on a distributed network of end user PCs with network access is a recipe for a bot net. Yes it’s doable but it’s not a magic wand to claim that an open platform will solve it. The magic of Travis was that with a couple clicks of OAuth you were signed up and running builds for your own PRs. My first thought upon seeing this years ago was “ How many people are using this to mine crypto?! “.
It's a bit more complicated than that.
I run gitlab and gitlab runners for a living, I can tell.
First thing first, you'd have to register a runner with a specific project. So no "arbitrary code".
Second thing, unless you can push a branch to the project main repository, no pipeline is ran. So for your own personal forks you'd either rely on gitlab.com-provided free minutes or you run your own runner (and tbh, it's fairly easy).
Last thing: you should not think of regular end-users. Think of middle to advanced users, that have a home server or something like that (homelabbers?).