TeamCity

Great DevOps tool

Vorteile:

Highly customizable pipelines, supporting multiple build steps with intelligent links and flows between them. Integration with Azure and Octopus Deploy are easy.

Nachteile:

Integration with Azure could be deepened, as at the moment it is done via an ad in rather then being natively supported.

Teamcity

Vorteile:

I am able to successfully manage over 600 projects in Teamcity in my environment. Updates are a breeze and downtime has been damn near zero in the five or six years I've used this product. The build configs are super flexible however I've not used another product so I'm not sure how my experience compares to the next.

Nachteile:

I'm not a huge fan of the experimental UI for some views but for other items I prefer it. I'm often switching back and forth between the two UIs

In Betracht gezogene Alternativen: Jenkins

Gründe für den Wechsel zu TeamCity: I wasn't part of that conversation as it was before my time but probably because we are an enterprise and require that level of support.

Nice Integrated CI

Vorteile:

It connects well with other JetBrains tools.

Nachteile:

It is not as popular as Jenkins so does not have as many plugins and the community using it is a lot smaller.

Not an easy tool, but does the job

Vorteile:

It does its job, and once you've set it up it's pretty solid. Agents and server have never needed a reboot as far as I know, and upgrades are quick enough. The integration with the VCS (SVN where I work) can let you keep track of what you have down the pipeline and, if you use the right tracking tool and add ticket numbers to the commit comments, you might find useful seeing what brought to that commit. If you often create new projects, the template feature can enormously speed up the process.

Nachteile:

It's very very easy to screw up. It gives you quite enough rope to hang yourself and your whole team twice, like creating dependencies among builds so that a simple commit can make the agents run for hours, or other amenities where you're not really sure what's the code you're building from (or, you might even be sure, but wrong!) If you're not well organized and don't know your way around the myriads of configurations, you may well end up not knowing what features you are deploying. It really needs some serious study before using it in production, and since it's not something you configure everyday, it's not easy to keep trained. In this perspective, the template feature will make you forget what's going on. Sadly, it's the only CI/CD tool I've ever used, so I can't compare it to anything else.

Best tool for build configuration,build history, and system maintenance in real time applications

Vorteile:

Every enterprise business uses this tool for maintaining their services enabled and establish the best business flow. All the services that are being build via Mule can be available via team city to be deployed.Its features include build history, user management and system maintenance. Build history has excellent feature of holding the various build version that are deployed earlier.Use service messages in your build scripts, interact via REST API, or create plugins for TeamCity using Open API. User Management has different ways of user authentication, and a log with all user actions for the transparency which can be used for tracking all activity on the server.Best feature is Version Control System(VCS) in which Team city in a single build it can take source code from different VCS Repositories.All the versions history is available environmental wise.

Nachteile:

The least of this software is there are some additional features required for the versions to avail across different enviroments like manual build configurations process can be avoided for the lower environments and UI part can be increased looking for new enhancements