3 ms·
I've used TeamCity (the UI has changed many times), Jenkins (including blue ocean), Bamboo, a few others... TeamCity is by far the best I've experienced. Jenki
by cosmotic 6y ago
I've used TeamCity (the UI has changed many times), Jenkins (including blue ocean), Bamboo, a few others... TeamCity is by far the best I've experienced.
Jenkins seems to suffer from too many cooks/anything goes mentality. It's clearly not well focused. It's feels like a handful of pet-projects lumped into one umbrella.
When it comes to functionality, TeamCity is constantly improving and innovating.
Based on the OP, I suspect their experience is with an old version or maybe misused or misconfigured.
- mumblemumble 6y agoI moved to TeamCity from Jenkins a few years ago. At first, I thought TeamCity's UI was batshit crazy. In retrospect, I think it was just that it's not organized at all like Jenkins is, and I needed to re-adjust my mental model for how the build server should work. Or something like that. All I know is that, at some point along the way, I came to use TeamCity to automate more things, while still spending less time futzing with it than I did with Jenkins. That said, I feel like TeamCity is also distressingly full of partially implemented features and flaky UX. It's just that its warts tend to accumulate on the periphery, rather than directly between me and the thing I'm trying to get accomplished before I can go home.
- m_mueller 6y agoI hated Jenkins on first sight but loved Teamcity. Its model is exactly how I imagined an ideal CI system to work. We use it in a minimal way though - a common git+ssh+make workflow that gets inherited to all project builds with only 3 params set in case a default doesn't work. So, I think it's about mental model as you wrote, plus where your techstack is in terms of unification (containerization helps there tremendously).