Live data from Hacker News

Travis CI acquired by Idera

blog.travis-ci.com

31–40 of 132 posts

Re: Travis CI acquired by Idera

#31
post #8

Circle CI has been steadily taking marketshare away from Travis for many, many years. And in my personal experience, mostly because of Travis' slow pace of improvement. Using containers for testing blows away performance on Travis for comparable tasks. Travis had made some improvements this last year to their workflows, configuration, and platform, but too little too late. My experience in dealing with their customer…

> Travis is obsolete, and they did it to themselves. This is sad, but the conclusion I have come to over the last 3-4 years as well. It was anybody's market 4 years ago, but through a sustained pace I think CircleCI have out-executed Travis consistently. The thing I find interesting is that, looking at Semaphore CI who used to be far behind Travis, they are now biting at the heels of CircleCI with their 2.0 iteration…

Semaphore v1 has been great and very simple to use. Huge fan of those guys. Bootstrapped, extremely friendly, helpful and competent. We’ve been using them since 2012.

v2 definitely looks promising but they’re not sunsetting v1. Lots of respect for that as well.

Edit: at the risk of sounding like a fanboy (I guess I am), they also grandfathered us indefinitely on the same price plan we signed. Not many companies do that sadly.

Re: Travis CI acquired by Idera

#32
post #29

Earlier quoted context omitted.

The main reason why we moved to CircleCI was due to the rising test flakes and outages in TravisCI. Also, TravisCI comes with a lot of crap pre-installed which can be a pain sometimes. With CircleCI you can provide your own custom Docker image for running the build. If the build fails there is even an option to SSH into the build to debug. This issue has a lot of details on what it takes to migrate an open source pro…

You can ssh and debug a travis build as well

But only on travis-ci.com, not for Open Source (.org) IIRC.

Re: Travis CI acquired by Idera

#33

Looking at Idera portfolio, I see Embracadero (Delphi developers for many years), Sencha (Ext.js), Assembla (was GutHub of Subversion era). So it seems like they buy companies and products that were big and very important among developersin the past, but not necessary leading the pack today. I didn't think of Travis in that regard, though in a past few month I started to see Circle CI badges popping here and there fo…

Looks like they bought Froala too, which is the best html editor we've used so far.

Re: Travis CI acquired by Idera

#35

Looking at Idera portfolio, I see Embracadero (Delphi developers for many years), Sencha (Ext.js), Assembla (was GutHub of Subversion era). So it seems like they buy companies and products that were big and very important among developersin the past, but not necessary leading the pack today. I didn't think of Travis in that regard, though in a past few month I started to see Circle CI badges popping here and there fo…

I've switched my personal projects, and my employer has switched to Circle over the past year. Circle's dockerized strategy for building up your CI/CD platform means that they support the new version of X nearly the day it comes out. Historically Travis has been very slow at this. Their support for Postgres 10 was an embarrassment (https://github.com/travis-ci/travis-ci/issues/8537). It's also vastly easier to parallelize your test suite. With Travis we had to install a third party gem to run our Rails' across many nodes. We also had to hand-manage balancing. With Circle we simply followed the docs, and we're off to the races.

Re: Travis CI acquired by Idera

#37
The main problem with Travis was that is stayed with the CI part (as the name suggests) while people wanted a CI/CD solution that helps with deployments and monitoring as well.

F.D. I work for Codefresh a full CI/CD solution (competitor to TravisCI)

Re: Travis CI acquired by Idera

#38
post #8

Circle CI has been steadily taking marketshare away from Travis for many, many years. And in my personal experience, mostly because of Travis' slow pace of improvement. Using containers for testing blows away performance on Travis for comparable tasks. Travis had made some improvements this last year to their workflows, configuration, and platform, but too little too late. My experience in dealing with their customer…

Does Circle-CI offers Mac runner for public/open-source projects? This is the reason I haven't been able to migrate from Travis to Circle-CI for all my projects, I have an open-source Electron module that I need to test cross platform so Travis covers Linux and Mac and AppVeyor for Windows.

> Does Circle-CI offers Mac runner for public/open-source projects

Yes, but you have to ask them to enable the thing. I used them for ArchMac before I migrated to GitLab. I am contemplating moving back to GitHub and CircleCI, unless I can get my hand on some decent hardware again to run the CI builds.

Re: Travis CI acquired by Idera

#40
post #32
post #29

Earlier quoted context omitted.

You can ssh and debug a travis build as well

But only on travis-ci.com, not for Open Source (.org) IIRC.

(Disclosure: Travis CI Employee)

We can do it on .org as well! Just need to reach out to us via email to enable it (as well as the instructions, as it requires a manual API call rather than a UI Button.) And, as Involans also mentioned, we are merging the two together.

support@travis-ci.com And we'll set you right up with debug mode. :)

Post reply on HN