(In case it's not super obvious, I work at CircleCI)
(In case it's not super obvious, I work at CircleCI)
- Privacy issues - Owning critical service component
Unfortunately I've never heard the reason that I think is the right one ( at least from what I can see is happening here ), which sounds like :
"Hey, we don't need this, because at Zalando / Nokia Maps, etc. we used Jenkins, so I don't wanna spend time maintaining a new tool ( CircleCI )."
Same stuff happens with project management ( dominated by JIRA around Berlin ).
At one point a company trashed all my CD-setup ( which was with the free plan anyway ) to run Jenkins with Docker ( I don't know how well supported docker is with CircleCI, but I doubt that is so much different than Jenkins ).
EDIT: I'm freelancing in Berlin, so I usually do a hand-over when the team of devs is hired.
That's ~$40k/year for 100 devs, plus the infrastructure costs. A Jenkins license is $0 (or $100k+ for enterprise support). If it was my budget, I'd have a hard time fronting up a large fraction of a developer's salary to a third party to provide a fuzzy level of support, versus spending zero money and putting the support burden on an in-house team I can trust and directly influence.
TeamCity has great support, I trust them from JetBrains's great work with IDEs, and their top-shelf license is ~$22k (one-off with 1-year of support & upgrade; iirc the yearly support fee is discounted 50% of original license).
Right now we're evaluating GitLab CI and it looks like the way forward (for us).
I appreciate that there's the option, but I'm thinking more along the lines of what Sentry offers: Open source, self-hostable for free, optional paid enterprise support, optional paid hosting for teams of all sizes. In my book that's the perfect lineup.
Travis doesn't offer self-hosting, Jenkins doesn't offer (non-enteprise) paid hosting.
CircleCI 2.0 was built with first-class Docker support, so if that's something you're interested in, definitely take a look.