News for hackers. Stuff that matters.
Re:Launching Today: CircleCI 2.0 Reaches General Availability by scrollaway on Tuesday July 11, 2017 @06:02AM (#14742839)
Yeah, CircleCI really needs to allow self-hosting. Jenkins is basically the only player in the space and Jenkins is not good.
Re:Launching Today: CircleCI 2.0 Reaches General Availability by nickcox on Tuesday July 11, 2017 @08:26AM (#14743525)
To be fair, there's also Concourse, TeamCity and GoCD which all enable self hosting for free.
Re:Launching Today: CircleCI 2.0 Reaches General Availability by jamesjamesm on Tuesday July 11, 2017 @08:46AM (#14743643)
And Drone CI which is the most similar to Circle CI
Re:Launching Today: CircleCI 2.0 Reaches General Availability by ssemmaprise on Tuesday July 11, 2017 @06:05AM (#14742851)
We do -- but let me know if for some reason this isn't what you're thinking/wouldn't meet your needs: https://circleci.com/enterprise/
Re:Launching Today: CircleCI 2.0 Reaches General Availability by falsedan on Tuesday July 11, 2017 @06:15AM (#14742888)
> $35/user/month

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).

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.
Re:Launching Today: CircleCI 2.0 Reaches General Availability by scrollaway on Tuesday July 11, 2017 @07:32AM (#14743244)
Like falsedan said, this doesn't cut it if you don't need an enterprise contract. My team for example: We're a 4-man self-funded startup and paying $140/month just for a license is super expensive, given that we can use Jenkins for free.

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.

Re:Launching Today: CircleCI 2.0 Reaches General Availability by manishas on Friday July 14, 2017 @12:12AM (#14767405)
Try Shippable's Startup edition @ $499/year. Though Jenkins software is free, you still pay for master and slave nodes. With Shippable Server SE, you can spin up nodes dynamically when builds are triggered, which will work out cheaper since you probably utilize your slave nodes less than 50% of the time.

https://aws.amazon.com/marketplace/pp/B072K2F5KF