"We are using the open-source version and there is a lot of plugins and features that are available and it works on agents for free. In other solutions, it will cost extra to use them with the agent."
"Jenkins can be used for elastic management, if you have any sensitive data or credentials you can use them across the environment. Additionally, the solution is easy to use and can be used across multiple use cases."
"Has enabled full automation of the company."
"Jenkins allows us to automate deployment, so I no longer have to do it manually. That's the primary use case. The other advantage of Jenkins is that it's open source. It was free for me to download and install. It's a product that's been in use for many years, so I can find a lot of support online for any issues that I may encounter while configuring anything for a given use case."
"The most valuable aspect of Jenkins is pipeline customization. Jenkins provides a declarative pipeline as well as a scripted pipeline. The scripted pipeline uses a programming language. You can customize it to your needs, so we use Jenkins because other solutions like Travis and Spinnaker don't allow much customization."
"The initial setup is simple."
"The auto-schedule feature is valuable. Another valuable feature is that Jenkins does not trigger a build when there is no change in any of the systems. Jenkins also supports most of the open-source plug-ins."
"It has a lot of community posts and support."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"The integration is a valuable feature."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"TeamCity's GUI is nice."
"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."
"The solution could improve by having more advanced integrations."
"The UI of Jenkins could improve."
"Sometimes, random errors of metadata are not there, which causes delays. These are essentially gaps in the information being passed to the job."
"Its schedule builds need improvement. It should have scheduling features in the platform rather than using external plug-ins."
"We cannot change the ownership of any directory or file or any kind of directory."
"The scriptwriting process could be improved in this solution in the future."
"A more user-friendly UI for creating pipelines would be helpful."
"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 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."
"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."
Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron.
TeamCity is a Continuous Integration and Deployment server that provides out-of-the-box continuous unit testing, code quality analysis, and early reporting on build problems. A simple installation process lets you deploy TeamCity and start improving your release management practices in a matter of minutes. TeamCity supports Java, .NET and Ruby development and integrates perfectly with major IDEs, version control systems, and issue tracking systems.
Jenkins is ranked 2nd in Build Automation with 23 reviews while TeamCity is ranked 5th in Build Automation with 4 reviews. Jenkins is rated 8.0, while TeamCity is rated 8.2. The top reviewer of Jenkins writes "We can do whatever we want and customize as much as we wish to in any programming language". On the other hand, the top reviewer of TeamCity writes "Scalable and simple to use with lots of very good plug-ins". Jenkins is most compared with Tekton, Bamboo, IBM Rational Build Forge, Digital.ai Release and Harness, whereas TeamCity is most compared with GitLab, Bamboo, Harness, CircleCI and AWS CodePipeline. See our Jenkins vs. TeamCity report.
See our list of best Build Automation vendors.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.