Jenkins vs TeamCity comparison

"I love Jenkins. I like that you work on anything, and you make anything. Jenkins is very important for my team. I am satisfied with the product."

"The most valuable feature of the solution is its integration between different tools."

"The most valuable features of Jenkins are its ease of use and good plugins available. You are able to connect to a lot of solutions."

"Jenkins's automation and orchestration features have significantly improved workflows by automating various processes. Initially, it did not support YAML manifesting or GitOps, but recent versions have introduced these capabilities. Now, the tool supports importing manifest files from Git repositories, enabling the implementation of GitOps pipelines. Compared to other tools like GitLab, it has become a mature tool for running CI/CD pipelines."

"Jenkins integrates with multiple tools like Bitbucket and makes life easier. We don't have to write a lot of code since a lot of libraries are available."

"There are a large number of plugins available for integration with third party systems."

"Jenkins' most valuable feature is Pipeline."

"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."

"I have not yet implemented the remote build feature, but this will be a big plus. We want to be able to build legacy products on a build agent without developers needing to have obsolete tool sets installed on their local PC."

"TeamCity is more structured and user-friendly than other vendors."

"It's easy to move to a new release because of templates and meta-runners, and agent pooling."

"Using TeamCity and emailing everyone on fail is one way to emphasize the importance of testing code and showing management why taking the time to test actually does saves time from having to fix bugs on the other end."

"The integration is a valuable feature."

"VCS Trigger: Provides excellent source control support."

"TeamCity is a very user-friendly tool."

"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."

"The product should provide more visualization as to how many pipelines are performing and how many builds are happening. It should also integrate with Kubernetes and OpenShift."

"Creating a new SonarQube project requires a separate job, and we've encountered some integration issues with Docker and the need for better vulnerability checks."

"Jenkins could have better cloud functionality. Currently, we are using the existing legacy model, but we are moving toward the cloud, so it would be great if they could improve in that area. In the future, I would like more cloud features and related training materials, like a video tutorial."

"There are a lot of things that they can try to improvise. They can reduce a lot of configurations. It is currently supporting Groovy for scripting. It would be really good if it can be improvised for Python because, for most of the automation, we have Python as a script. It would be good if can also support Python. We have a lot of Android builds. These Android builds can be a part of Jenkins. It can have some plug-ins or configurations for Android builds. There should also be some internal matrix to check the performance. We also want to have more REST API support, which is currently not much in Jenkins. We are not able to get more information about running Jenkins. More REST API support should be provided."

"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on."

"Jenkins is not an easy solution to use and the configuration is not simple. They can improve the solution by adding a graphical interface that is more user-friendly."

"The learning curve is quite steep at the moment."

"The upgrades need improvement."

"REST API support lacks many features in customization of builds, jobs, and settings."

"The UI for this solution could be improved. New users don't find it easy to navigate. The need some level of training to understand the ins and the outs."

"Last time I used it, dotnet compilation had to be done via PowerShell scripts. There was actually a lot that had to be scripted."

"If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal."

"The integration between other solutions and TeamCity could be smoother."

"Their online documentation is fairly extensive, but sometimes you can end up navigating in circles to find answers. I would like them (or partner with someone)​ to provide training classes to help newcomers get things up and running more quickly."

"We've called TeamCity tech support. Unfortunately, all their tech support is based in Europe, so we end up with such a big time crunch that I now need to have one person in the US."

"Integrating with certain technologies posed challenges related to time and required support from the respective technology teams to ensure smooth integration with TeamCity."

"The open-source version is free, but small companies would not be able to afford the cloud-based version."

"The solution is open source."

"It is a cheap solution."

"Jenkins is a free open-source server."

"​It is free.​"

"It's free software with a big community behind it, which is very good."

"I used the free OSS version all the time. It was enough for all my needs."

"We use the tool's open-source version which is free. There is an enterprise version which is expensive but comes with better support."

"The licensing is on an annual basis."

"Start with the free tier for a few build configs and see how it works for you, then according to your scale find the enterprise license which fits you the most."