3 ms·
I have used Jenkins many times and it's always worked fine. But I always wish TeamCity was more widely adopted and deployed. Sure, it costs money, but so does I
by paloaltokid 10y ago
I have used Jenkins many times and it's always worked fine. But I always wish TeamCity was more widely adopted and deployed. Sure, it costs money, but so does IntelliJ. And it's completely worth it.
- insulanian 10y agoCan you list few reasons why you prefer TeamCity?
- paloaltokid 10y agoMuch nicer UI, nice support team at JetBrains. I found plugin writing to be pretty friendly once I got it set up though I've never written a Jenkins plugin to be fair. Also very easy to define build pipelines in the UI. See 'CraigJPerry answer also.
- CraigJPerry 10y agoI had never touched TC until my current role. I'm dumbfounded that they don't demo it more. - You can backup / restore / version your entire CI config to a file = move fast and break stuff because it's easy to revert - Build chains (pipelines in Jenkins) are built in, they're smarter than the average bear too - Plugins not required, everything just works out the box, from report publishing to maven builds to connectivity with obscure VCS's - it's all just built in and there's no faffing about looking for combinations of plugins which play well together To get started is as easy as any other CI server, however, because it's quite a bit more powerful than any other CI i've used, i'd say it takes a minute or two to fully appreciate what's on offer.