Ask HN: Is the CI space overcrowded?

7 points by Scorpiion 8 years ago | 20 comments

Hosted CI is a hot space, and fairly recently the git hosting providers (Bitbucket and Gitlab) also entered the game with their own hosted services. Some hosting providers also have some overlap with CI functionality or specific CI services on their own. I wonder what people in the HN community thinks about the CI space as of today.

1. Do you think it's overcrowded? Is there space for new companies or is CI basically a "solved problem"? If not what do you dislike with current offerings?

2. Do you prefer a third party CI as compared to the hosting provider offering their own CI at a lower price? Assuming here that the hosting provider would offer lower price because their main income is from the 24/7 hosting fees. Or would you simply switch to the hosting providers CI if it was good?

Disclosure: I am the founder Sourcevoid, a cloud/PaaS company. I'm a little split on how much CI functionality we should integrate into our platform, compared to just trying to promote third party CI providers instead. We already do a fair amount via our build system, but at the same time CI is more than just the build process of course. This question is not about our company or our offerings, I just think it's an interesting question to discuss.

lomnakkus 8 years ago |

I find that it's just like the bug tracker space: There's a lot of contenders, but somehow none of them actually hits the sweet spot.

For CI, it's either: "too GUI" or "not enough programmable".

Also, CI is an area that absolutely cries out for container technology, but the state of containers on Linux[1] is absolutely abysmal. Maybe it'll be better in ~5 years when we'll hopefully be about 40% towards the capabilities with Solaris Zones. (Here's a hint: If you cannot fully 'contain' root and users/mounts/devices, then you're not being serious.)

[1] The most popular platform for this, by a far margin.

dasmoth 8 years ago | |

I think an aspect of the problem is that most tools in this space actually get sold to project managers (and secondarily, process-oriented senior engineers), not hackers who just want to shut the door, quit Slack, and build stuff.

I think it's interesting to consider what hacker-oriented tools might look like. GitHub close to launch might qualify: simple interface, a model where (at least conceptually) projects are owned by individuals not organisations, and a simple but pretty pleasant-to-use issue tracker with no "workflow" type mechanisms. A lot of this has changed now (support for mandating code reviews!) and from a revenue point of view I'm not sure they're wrong to do these things. But it was the simple, hacker-friendly version that got them their initial mindshare.

I'm not entirely sure what the GitHub 1.0 of CI would look like, but probably not like the current offerings.

a-saleh 8 years ago | |

Which camp of "too GUI" or "not enough programmable" does jenkins fall in?

How would the sweet-spot look like?

lomnakkus 8 years ago | | |

"not enough programmable", but I'll add the caveat that I haven't really caught up with the 2.x bits that I think could help quite a bit.

(However, from the documentation I got the impression that the new 2.x Jenkins bits were quite repository-centric. It turns out that what I want is really to define the whole CI infrastructure separately from my repos with a few rules to generate appropriate jobs, etc. Perhaps the solution to that is to just define a repo for all-the-builds? Still need to look into it.)

shubhamjain 8 years ago |

Nathan: You’ve shown with Freckle that you can enter a saturated market like time tracking and still do well.

Amy: “Saturation” is a load of bullshit :)

Nathan: Really it just shows the market exists.

Amy: It’s more than that. So much more than that. If a million people use Harvest, there’s no way they’re all served well by the same tool. The presence of other products doesn’t just show opportunity, it CREATES opportunity. Because wherever there’s a big biz, there will be lots of dissatisfied customers.

Source: https://stackingthebricks.com/difficulties-for-nathan-barrys...

debacle 8 years ago |

If you could make a self-hosted Jenkins replacement that is even half as good as Jenkins (think extensions) but written in not Java, I think it'd receive a lot of positive reception.

The trick with CI, like task/project management software, is that people don't look at what works. They don't try and compete on intrinsics like stablility, extensibility, etc, and really after 12 months on any platform, any mid-large size company is going to care more about those things than new shiny.

Jenkins had the absolute worst UI for a long time, and it still was many people's top choice for CI. You're generally writing a tool for programmers, after all.

twobyfour 8 years ago |

It's a well-populated space. If you're going to enter it, you need to be clear about differentiation.

We picked our CI solution because it was the only cloud offering we could find that supported Bitbucket and also allowed us to set up our own fully-custom environments to run against - without Docker.

Sadly, it took about a week's worth of research to figure that out. And I'm a bit concerned that in this crowded market they'll go out of business and leave us high and dry.

rjbwork 8 years ago | |

This sounds a lot like my requirements...can you tell me your CI provider?

twobyfour 8 years ago | | |

https://buildkite.com

We migrated there from Bamboo Cloud when Atlassian discontinued it. It's nearly a direct drop-in replacement, and they even had docs specifically about Bamboo migrations. Their customer support during onboarding was also superb, and they've been responsive to feature requests. We've been using it for almost a year now, and overall we're pretty pleased.

What are you using currently?

twunde 8 years ago |

I think that as evidenced by the discussion about concourse ci today https://news.ycombinator.com/item?id=14785254 that there is still room for improvement and new products, especially on-prem CI tools like Jenkins/TeamCity/Bamboo/Concourse.

jetblackio 8 years ago | |

One thing that I've always wanted was for Jenkins to get away from being a UI, and just be an engine with a nicely documented API. People could then build more niche CI/CD systems on top of that engine without having to reinvent the wheel. It's nice that Jenkins is finally getting a UI facelift though.