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, Amazon Web Services (AWS) and others in Build Automation."The tool helps to integrate CI/CD pipeline deployments. It is very easy to learn. Its security model is good."
"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."
"I like GitLab from the CI/CD perspective. It is much easier to set up CI/CD and then integrate with other tools."
"The most valuable feature of GitLab is its convenience. I am able to trace back most of my changes up to a far distance in time and it helps me to analyze and see the older version of the code."
"I have found the most valuable feature is security control. I also like the branching and cloning software."
"The solution is stable."
"GitLab is very well-organized and easy to use. Also, it offers most features that customers need."
"GitLab is a solution for source code management, container registry, pipelines, testing, and deployment."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"It is very useful for us to be able to collect and manage automatic processing pipelines."
"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."
"We used it for all continuous integration parts, like automation testing, deployment, etc."
"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."
"I am not aware of the available options in the market right now compared to Jenkins, but I am pretty much happy with the service that Jenkins is providing our company."
"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 most valuable features are Jenkins Pipelines for ALM and full Deploy Cycle."
"One of the most beneficial features for us is the flexibility it offers in creating deployment steps tailored to different technologies."
"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."
"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."
"We would like to see better integration with other version controls, since we encountered difficulty when this we first attempted."
"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."
"It provides repeatable CI/CD throughout our company with lots of feedback on failures and successes to the intended audiences via email and Slack."
"The integration is a valuable feature."
"TeamCity is a very user-friendly tool."
"It could have more security integrations and the ability to check the vulnerability of the code. I don't think it is a responsibility of Gitlab, but it would be nice to have more options to integrate with."
"The documentation is confusing."
"I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities."
"Expand features to match other tools such as a static code analysis tool so third-party integrations are not required."
"The documentation could be improved to help newcomers better understand things like creating new branches."
"We'd always like to see better pricing on the product."
"We would like to generate document pages from the sources."
"Based on what I know so far, its integration with Kubernetes is not so good. We have to develop many things to make it work. We have to acquire third-party components to work with Kubernetes."
"Performance-wise. This needs to be improved. Not only performance-wise, some functionality or some features can be added to Jenkins."
"I would like them to provide space for people to have a central node that stores all the logs of workspace information in a distributed fashion to facilitate backup and restoration. Currently, everything is stored on one node, so you need to set up distributed storage or an endpoint that you can use for backing up your information."
"Jenkins is an old product, and we encounter performance issues and slow response. Also, some of the plugins are not stable."
"It does not have a very user-friendly interface."
"It can be improved by including automated mobile reporting integrations."
"I sometimes face a bottleneck when installing the plugins on an offline machine. Mapping the dependencies and then installing the correct sequence of dependencies is a nightmare, and it took me two days to do it."
"Tasks such as deployment, cloning, database switchover, and all other database missions and tasks are being done through Jenkins. If a job does not go through, at times the error message does not clearly indicate what caused the failure. I have to escalate it to the Jenkins DevOps team just to see what caused the failure. If the error message is clear, then I wouldn't have to escalate the issue to different teams."
"UI is quite outdated."
"It will benefit this solution if they keep up to date with other CI/CD systems out there."
"If there was more documentation that was easier to locate, it would be helpful for users."
"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."
"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."
"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."
