Here is a summary I found online comparing Drone, Travis, and Jenkins, all of which were brought up at the meeting today: https://stackshare.io/stackups/drone-io-vs-jenkins-vs-travis-ci
Having just spent a couple of months updating Jenkins to the new Pipelines that supposedly solve all problems, I’m not super keen on switching to something as untested and relatively unused in production as Drone is, unless anyone knows someone who uses it?
Travis might be interesting to try self-hosted but Travis has been pretty flaky for us even just doing our simplest and least taxing tests and I find it more difficult to debug when something does go wrong, but maybe others have different feelings about the differences?
I have no opinion about drone vs Jenkins. I just want something that works! That switch to pipelines seemed like it was a lot more effort than anticipated. And it doesn’t seem like it solved all the issues at hand. Anyway, this is the main reason I hesitate to replace things that work unless I see it working. It’s way too easy to claim it works on paper and it’s a lot easier to verify that it does or doesn’t once it’s done.
And I want to +1 that very heavily.