Congrats to the founders, that I met during a conference, super developers.
Thanks for the contribute to the open source projects!
Travis CI acquired by Idera
21–30 of 132 posts
Re: Travis CI acquired by Idera
#22Circle 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…
I’ve had a similar experience. It seems like Travis rested on its past reputation for a long time and Circle slowly eroded their lead with a much better platform.
Circle was way ahead of Travis in their docker implementation. The Travis docker stuff always felt like a hack.
Once I started moving more projects to Circle, most of the developers on our team were much happier on Circle.
Re: Travis CI acquired by Idera
#23Earlier quoted context omitted.
Yeah, I've been seeing lots of people switch to circle-ci or gitlab over the past year. Not totally sure why. Travis does what I need and I know how to use it, and I don't particularly want to learn something new for CI myself, I just want to code!
CircleCI has a free tier for private repos, same with Gitlab.
The private repo pricing was what drove me to try an alternative to Travis in the first place. The cheapest private repos plan is $70/mo now and, if memory serves, when I looked into it previously it was >$100/mo.
Fine for startups I guess. For the use case of someone who wants a CI server that, say, runs tests on their Project Euler private repo it's a no-way-no-how price point.
I assume they've thought this through and it's done purposefully. Still, side projects tools are a gateway to real project usage.
Re: Travis CI acquired by Idera
#24Looking 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…
Yeah, I've been seeing lots of people switch to circle-ci or gitlab over the past year. Not totally sure why. Travis does what I need and I know how to use it, and I don't particularly want to learn something new for CI myself, I just want to code!
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 project from Travis CI to CircleCI if you are interested.
https://github.com/zulip/zulip/issues/7748
Re: Travis CI acquired by Idera
#25Looking 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 actually seen (and need to do so myself) a few migrate to(or move even more into) Travis because they've added Windows builds. AFAIK they're the only hosted CI that offers Linux, Mac, AND Windows builders.
Re: Travis CI acquired by Idera
#26I've been worried about travis' lack of urgency in dealing with the fact that the existing travis-ci.org github hooks used for open source products are going to stop working in a week or two... https://github.com/travis-ci/travis-ci/issues/9745 Now bought by a private equity firm, which usually doesn't indicate lots of innovation or an increase in quality on the way. I wonder if I should be worried and start migratin…
Hey there,
(Disclosure: Travis CI Employee)
The migration from GitHub hooks is actually just about complete. You can see the changelog entry here: https://changelog.travis-ci.com/migrating-from-github-servic...
Apologies for the lack of public updates on this!
Re: Travis CI acquired by Idera
#27Looking 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 actually seen (and need to do so myself) a few migrate to(or move even more into) Travis because they've added Windows builds. AFAIK they're the only hosted CI that offers Linux, Mac, AND Windows builders.
Azure Pipelines was the first one, and would probably have a better service overall if they had better documentation and supported more languages/environments.
Re: Travis CI acquired by Idera
#28Circle 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.
It's worth noting that Travis also supports windows builds now. Which to me is a HUGE value proposition over CircleCI.
Re: Travis CI acquired by Idera
#29Earlier quoted context omitted.
Yeah, I've been seeing lots of people switch to circle-ci or gitlab over the past year. Not totally sure why. Travis does what I need and I know how to use it, and I don't particularly want to learn something new for CI myself, I just want to code!
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
Re: Travis CI acquired by Idera
#30Circle 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…
Thanks for mentioning Semaphore, cofounder here. Yes, we’re 100% bootstrapped and in this for the long haul. It’s really all about execution. We built 2.0 in a timeframe in which we’d previously ship one or two features. Of course years of domain experience help, but everyone from Fred Brooks to DHH is right — adding more people won’t help build a better product faster.