3 ms·
Not too shocking, unfortunately, from discussion when the acquisition was annoucned (https://news.ycombinator.com/item?id=18978251 https://news.ycombinator.com/
by jrochkind1 8y ago
Not too shocking, unfortunately, from discussion when the acquisition was annoucned (https://news.ycombinator.com/item?id=18978251 https://news.ycombinator.com/item?id=18978251), we knew that this was the kind of private equity firm that makes money by buying products with existing revenue streams, and then _not_ investing in them.
(And the corollary, laying off staff you don't need if you're not going to be investing in it, obviously helps your profit margin).
This is kind of how private equity works.
It is sad, I had really liked travis as a product, I don't expect I will be able to continue to.
Travis is just _so easy_ to set up for my basic ruby gem and Rails app projects (I don't want to spend time on setting up CI, I just want it to be done), as well as free for open source -- none of it's competitors have seemed to give me that when I looked before.
Travis, by offering an absolutely brain-dead setup, and giving it away free to open source, really created a revolution in actually doing CI for open source, at least in ruby. Everyone's doing CI now, when few open source projects were before in ruby. That anyone offers free CI for open source at all is probably due to the need to compete with travis. I wonder if it'll stick around.
- FanaHOVA 8y agoAlways used Circle in my Rails app, works very nicely (even though the web experience has been going downhill a little bit lately).
- simonbyrne 8y agoAgree 100%. Free CI really did provide a massive boost to collaborative open source projects. As a user, it did a lot to increase software quality: not just catching inadvertent bugs, but also ensuring that there was at least some reproducible way to get the code working, that didn't depend on some implicit configuration of the authors system. As a maintainer, accepting simple pull requests becomes much easier when you can quickly look over the code and check the CI status, and not have to try it out locally yourself. It was certainly critical to the "social coding" idea behind GitHub. So thanks to the team that put it together. Even if the product you built doesn't live on in the way you hoped, it has certainly had a lasting impact for the better on the open source world.