Earlier quoted context omitted.
That's exactly what they do, and the reason is that there is a long tail of subscription revenue that will continue to trickle in. They monetize that very well (for the owners)
Honestly, for enterprise users that is a good thing. In the hands of a company like Idera we can be reasonably confident that Travis will not disappear anytime soon. Under independent - or forbid Oracle / Google stewardship - that is far less certain.
Travis CI acquired by Idera
81–90 of 132 posts
Re: Travis CI acquired by Idera
#82Looking 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.
I hear Appveyor and Azure Pipelines are the two most usable Windows build systems; I'm quite happy on Appveyor.
Re: Travis CI acquired by Idera
#83Earlier quoted context omitted.
Looks like they bought Froala too, which is the best html editor we've used so far.
What does the $144 Froalo offer that open source alternatives don't? Serious question. The Froalo site is not convincing at all.
It's not as fancy as the abstracted editors that have their own non-DOM format structure but they usually are missing many other features.
The pricing has increased and the hobby plan probably isn't worth it but the product itself is good if you need an editor.
Re: Travis CI acquired by Idera
#84Re: Travis CI acquired by Idera
#85Re: Travis CI acquired by Idera
#86Earlier quoted context omitted.
Personally, I've seen growing stability issues. Builds are failing for no apparent reason and work fine after a manual restart. Circe CI was the next free service to try.
FWIW, I'm currently using Circle for several builds, and am actually looking at alternatives now. The web interface has been falling over (which is highly disruptive to developers when they can't look at build results and trigger deploys, etc). Circle has some nice features (especially easy artifacting and splitting rspec tests based on historic run-time) but it's not enough to overcome the lost momentum and producti…
I've been very happy with Buildkite so far. The web interface fits my mental model of how things should work much better than CircleCI's ever did.
Our primary reason for switching was CircleCI's unpredictable and high costs on the iOS side (per minute billing combined with slow builds -> monthly fees in the price range of a new Mac mini).
Our Android builds are now about 10 times as fast at the same price.
The savings and the performance benefits are of course wholly due to the bring-your-own-build-machines approach that Buildkite takes. I don't see that as much of a hardship, though, especially since CircleCI 2.0 removed a lot of the "it just works" magic in favor of your own build scripts and Docker images. Preparing the build agents is not significantly more work.
Re: Travis CI acquired by Idera
#87Earlier quoted context omitted.
We switched from Travis CI to Circle CI because Circle CI was (a) significantly faster and (b) a little cheaper
We made a smilar decision in 2017. The reason was that our builds were stupidly slow because travis uses cheap instances. There was no option to fix that other by allowing more concurrent builds. Travis has no feature to actually allow users to have reserved instances of a particular type. Money was not the issue; the feature does not exist. Builds were taking up to 20 minutes and with multiple team members doing prs…
Re: Travis CI acquired by Idera
#88Expect layoffs and all future work to be outsourced via fixed cost development to lowest bidders (mostly in India). Also expect a big sales push for multi year contracts.
Nothing wrong with India, just that companies like Idea don't like to have developers on payroll, and the ones that do write specs all day long.
Re: Travis CI acquired by Idera
#89Earlier quoted context omitted.
> 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.
Re: Travis CI acquired by Idera
#90Earlier quoted context omitted.
That's exactly what they do, and the reason is that there is a long tail of subscription revenue that will continue to trickle in. They monetize that very well (for the owners)
Honestly, for enterprise users that is a good thing. In the hands of a company like Idera we can be reasonably confident that Travis will not disappear anytime soon. Under independent - or forbid Oracle / Google stewardship - that is far less certain.
* this is a comment from me personally and not an official company statement.