21–30 of 193 posts
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).
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…
"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 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 project)
To me, that seems to say if someone commits code while on the clock, that is employees paid to work on the project.
That definitely disqualifies a huge number of open source projects, probably the majority, right?
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…
"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…
> Your project does NOT provide commercial services (such as consulting or training) around the software, and does NOT distribute paid versions of the software
Jetbrains should really take it to the next level and require all developers on your open source project to provide up-to-date proof of unemployment benefits.
I long ago switched to CircleCI for all my builds-- it has free builds for both open source and private repositories with a simple (and comparatively inexpensive) pricing plan based on parallel builds with Windows, macOS and Linux build containers. With Github Actions on the scene now, I don't see much reason to use Travis over one of the alternatives.
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?! “.
Having worked at a Travis CI competitor that also offered open-source credits. The answer is "many" if you don't do anything about it...
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…
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…
>intentional manipulative dishonesty 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.
I think the far more likely explanation is that updating the websites was very low on the priority list of the people who made this decision.
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…
Ah, Jeff, actually thanks to your post I saw that most of the projects I contribute to had Travis CI builds take almost a day and I went over most of those that used free TravisCI/CircleCI/Semaphore and started migrating them all to Github Actions. So again, thank you for your particular inscription on the blog, I guess.
I just got an OSS project wired up using TravisCI. And during that process, I noticed OSS builds had a backlog of 5000+ jobs. It took sometimes 45 minutes for my build to process. It's a shame. Something like this should exist, but I can't blame them for not wanting to do it for free.