Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Travis CI acquired by Idera

blog.travis-ci.com

Post reply on HN
Print view View original

91–100 of 132 posts

Re: Travis CI acquired by Idera

#91

Post by jrochkind1 »

DrTorte wrote: post #26
jrochkind1 wrote: post #11

I'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!

Thanks! Good to know.

Really kind of down to the wire though, eh?

It would be really disastrous if the deadline were to be missed, but even if it goes smoothly in the end, how it's been handled does not inspire confidence. One documentation page still says "The migration was planned to start at the end of Q2 2018, but has been pushed back. We will announce a new date as soon as we are able." --https://docs.travis-ci.com/user/open-source-on-travis-ci-com...

Re: Travis CI acquired by Idera

#92

Post by jrochkind1 »

epage wrote: post #59
jrochkind1 wrote: post #9

Earlier 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!

I feel dirty for saying this but Azure Pipelines is the service that is tempting to me because of the power of its file format (variable substitution, conditionals, template tasks and steps).

Curious if anyone has used Azure Pipelies with Rails projects and has a review.

(Yeah, I know, all these CI things are hypothetically platform agnostic, but then there's reality, different platforms-under-test have different sorts of problems which become priorities for the CI platform to smooth out and make just work, or don't).

Re: Travis CI acquired by Idera

#93

Post by williamdclt »

mnutt wrote: post #80
williamdclt wrote: post #47

Earlier quoted context omitted.

We usually use CircleCI at my company. I never realised how good I had it until I had to use Travis at my current project :) To give an example: we have a monorepo and it's impossible to only run the tests of the project that has been updated. Even if you're ready to hack around with git. Even if you're ready to hack around with Travis internal functions. Because TRAVIS_COMMIT_RANGE is just broken. And your argument…

We also use travis + a monorepo and yeah TRAVIS_COMMIT_RANGE is broken. We end up just tagging successful master builds and generating our commit range off of that. But yeah, so much of it is flaky, and the pricing is noncompetitive. Our current iteration has travis's docker client tunneling to an ec2-based docker server; it's both cheaper and faster and will hopefully make it easier to rip out Travis in the future.

Not a bad idea but travis only does a shallow clone, do you unshallow it? Doing a `git fetch --unshallow` was slow, and hanging forever about one time out of 5 when I tried a few weeks back

Re: Travis CI acquired by Idera

#94

Post by williamdclt »

MapleWalnut wrote: post #58
williamdclt wrote: post #47

Earlier quoted context omitted.

We usually use CircleCI at my company. I never realised how good I had it until I had to use Travis at my current project :) To give an example: we have a monorepo and it's impossible to only run the tests of the project that has been updated. Even if you're ready to hack around with git. Even if you're ready to hack around with Travis internal functions. Because TRAVIS_COMMIT_RANGE is just broken. And your argument…

Don't you need to do the same hacking within CircleCI?

I do, but at least it is feasible (at least I think, never actually needed to do it). With Travis, even being willing to hack around, I just didn't manage to get it working at all

Re: Travis CI acquired by Idera

#95

Post by edaemon »

jrochkind1 wrote: post #9
andrewl-hn wrote: post #3

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…

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!

I've chosen CircleCI over Travis for some projects because CircleCI is free for private repositories (to an extent). Travis is only free for open source, and is slightly more expensive for similar resources.

Of course that doesn't explain why open source projects would switch, but it could just be a mind share thing.

Re: Travis CI acquired by Idera

#96

Post by papasound »

TheJimMcKeeth wrote: post #90
dotancohen wrote: post #60

Earlier quoted context omitted.

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.

As an employee of Embarcadero I can tell you they do invest in new development. Delphi has received a number of new features and updates since Idera aquired us. Could they invest more? You can always invest more, but it is important for the long term that the company and products continue, which Idera seems good at. * this is a comment from me personally and not an official company statement.

Do you think they will have enough money to fix gazillion of RIO bugs? Cause i have a feeling that Delphi is is getting out of tracks and nobody cares about it anymore? But i wish i am wrong since i like it very much.

Re: Travis CI acquired by Idera

#97

Post by ElFitz »

epage wrote: post #59
jrochkind1 wrote: post #9

Earlier 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!

I feel dirty for saying this but Azure Pipelines is the service that is tempting to me because of the power of its file format (variable substitution, conditionals, template tasks and steps).

I never believed I'd ever pick a Microsoft product over anything else.

And yet, here we are... Azure Pipelines

Edit: VS Code too

Re: Travis CI acquired by Idera

#98

Post by ArturT »

jherdman wrote: post #35
andrewl-hn wrote: post #3

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 para…

I work on knapsack gem to split tests across parallel CI nodes. To do optimal balancing I developed a dynamic test suite split with Queue approach.

Here is example for Travis CI https://docs.knapsackpro.com/2018/how-to-run-travis-ci-paral...

And this is the graph showing the difference if you compare knapsack_pro dynamic tests split with what CircleCI does which is basically only time-based split. https://docs.knapsackpro.com/2018/improve-circleci-paralleli...

Re: Travis CI acquired by Idera

#99

Post by Rapzid »

Lots of issues with Travis CI feature velocity as well. Most of the other pain points others have mentioned I have felt. Random build failures, network issues, and etc.

A particular issue is the PR merge-commit builds. Between stages a merge/push into master can change the merge-commit! This means code between stages can diverge. You may build an artifact in one stage, then run an out-of-date test suite against it in another. Known issue for years, had an employee acknowledge months ago on the community forum then.. Nothing.

Another pain point that is not unique to Travis, is the lack of true "pipelines". Inter-project builds are a complete DIY crap fest. Coupled with roll-your-own artifact storage and retrieval.. Self-hosted solutions like Bamboo and TeamCity(Bamboos superior IMHO) are light years ahead of the SaaS solutions I've viewed.

Test report analysis is another big feature missing from most. Would be good to be able to visualize and report on tests. I was almost considering this being a valid stand-alone SaaS idea because nobody has it!

I believe the future of our integration/system tests will be build on codepipelines or the like for scale. Travis or CircleCI will be the public facing component.

Re: Travis CI acquired by Idera

#100

Post by Rapzid »

andrew_ wrote: 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…

On a tangent and just because these discussions almost never happen; Jfrog has been my most terrible support experience. We have an OSS and paid plan and I expect 4+ days before hearing back from them. If/when are repos experience an issue we would be dead in the water. I have even tried calling their emergency contact number with no answer or call-back.
Post reply on HN