We performed a comparison between GitLab, Jenkins, and TeamCity based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation."It scales well."
"The dashboard and interface make it easy to use."
"The stability is good."
"GitLab is kind of an image of GitHub, so it gives us the flexibility to monitor our changes in the repos."
"GitLab's best feature is Actions."
"A user friendly solution."
"GitLab integrates well with other platforms."
"I like that you can use GitLab as a double-sided solution for both DevOps and version management. It's a good product for working in these two areas, and the user interface makes it easy to understand."
"The solution is scalable and has a large number of plugins that can help you scale it to your needs."
"Automation of chores like deployment, frequent manual tasks (like running scripts on test and production systems) reduced the time used and the number of errors made by engineers, freeing them to do meaningful work instead."
"Jenkins has a lot of built-in packages and tools."
"We significantly reduced build times of large projects (more than 80k lines of Scala code) using build time on Jenkins as a time sample. It reduced the developer write-test-commit cycle time, and increased productivity."
"The initial setup is pretty simple."
"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."
"A lot of support material exists via a single web search of exactly what you're looking for."
"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."
"Time to deployment has been reduced in situations where we want to deploy to production or deploy breaking changes."
"Good integration with IDE and JetBrains products."
"The integration is a valuable feature."
"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."
"It's easy to move to a new release because of templates and meta-runners, and agent pooling."
"The flexibility of TeamCity allows it to fit in workflows that I have yet to imagine."
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"The most valuable aspect of the solution is its easy configuration. It also has multiple plugins that can be used especially for building .net applications."
"I've noticed an area for improvement in GitLab, particularly needing to go through many steps to push the code to the repository. Resolving that issue would make the product better. My team quickly fixed it by writing a small script, then double-clicking or enabling the script to take care of the issue. However, that quick fix was from my team and not the GitLab team, so in the next release, if an automatic deployment feature would be available in GitLab, then that would be good because, in Visual Studio, you can do that with just one click of a button."
"The solution should again offer an on-premises deployment option."
"It's more related to the supporting layer of features, such as issue management and issue tracking. We tend to always use, for example, Jira next to it. That doesn't mean that GitLab should build something similar to Jira because that will always have its place, but they could grow a bit in those kinds of supporting features. I see some, for example, covering ITSM on a DevOps team level, and that's one of the things that I and my current client would find really helpful. It's understandably not going to be their main focus and their core, and whenever you are with a company that needs a bit more advanced features on that specific topic, you're probably still going to integrate with another tool like Jira Service Management, for example. However, some basic features on things like that could be really helpful."
"For as long as I have used GitLab, I haven't encountered any major limitations. However, I think that perhaps the search functionality could be better."
"Some of the scripts that we encountered in GitLab were not fully functional and threw up errors."
"I would like to have some features to support peer review."
"The solution should be more cloud-native and have more cloud-native capabilities and features."
"We would like to have easier tutorials. Their tutorials are too technical for a user to understand. They should be more detailed but less technical."
"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."
"The documentation could be more friendly, and more examples of how to use it."
"There are some difficulties when we need to execute the DB script."
"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on."
"Logging could be improved to offer a clearer view."
"The bug fix speed is very slow."
"Jenkins could improve by adding the ability to edit test automation and make time planning better because it is difficult. It should be easier to do."
"A more user-friendly UI for creating pipelines would be helpful."
"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."
"REST API support lacks many features in customization of builds, jobs, and settings."
"If there was more documentation that was easier to locate, it would be helpful for users."
"I need some more graphical design."
"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."
"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 upgrade process could be smoother. Upgrading major versions can often cause some pain."
