Re:Launching Today: CircleCI 2.0 Reaches General Availability
by gtirloni on Tuesday July 11, 2017 @07:05AM
(#14743115)
If you have 100 devs, you need at least 1 FTE supporting Jenkins and that's $60-120k/year alone.
Re:Launching Today: CircleCI 2.0 Reaches General Availability
by falsedan on Tuesday July 11, 2017 @08:28AM
(#14743535)
We have more devs than that, and we spend way less than 1 FTE (or equivalent) per year on keeping it in good working order. Our biggest issue is when we want to do something that's not well-supported or hit bugs.
Re:Launching Today: CircleCI 2.0 Reaches General Availability
by gtirloni on Tuesday July 11, 2017 @09:52AM
(#14744140)
That's impressive. We run into not well supported features and bugs frequently. It's probably a side effect of our workloads.
Right now we're evaluating GitLab CI and it looks like the way forward (for us).
Re:Launching Today: CircleCI 2.0 Reaches General Availability
by falsedan on Tuesday July 11, 2017 @03:39PM
(#14747315)
Don’t get me wrong, we are owned daily by Jenkins bugs. We just push as much as possible out of job config and into shared workflows & Makefiles, and treat Jenkins as a glorified cron with a web UI.
Re:Launching Today: CircleCI 2.0 Reaches General Availability
by sixstringtheory on Tuesday July 11, 2017 @08:23AM
(#14743514)
Nah, just have everyone spend 1% of their time on CI.
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).