We performed a comparison between CircleCI, GitLab, and Jenkins based on real PeerSpot user reviews.
Find out what your peers are saying about GitLab, Jenkins, Google and others in Build Automation."The automation workflow in CircleCI related to third-party applications is very good and allows standardization of applications."
"Some of the most valuable features include container-based builds, integration with Bit Bucket and being able to store artifacts."
"The solution offers continuous integration and continuous delivery."
"The ability to automate the build process in a seamless way and run workflows effortlessly. It supports parallel builds so it can scale well. Also, it covers the basics of any build and integration tool, including email notifications (especially when tests are fixed), project insights, etc."
"Enables us to detect exactly which build failed and why, and to push multiple builds to our production environment at a very fast rate."
"It's a stable product."
"GitLab is kind of an image of GitHub, so it gives us the flexibility to monitor our changes in the repos."
"CI/CD is very good. The version control system is also good. These are the two features that we use."
"GitLab integrates well with other platforms."
"The most valuable feature of GitLab is the automatic merging of code."
"The user interface is really good so that helps with huge teams who need to collaborate."
"The solution's most valuable feature is that it is compatible with GitHub. The product's integration capabilities are sufficient for our small company of 35 people."
"The most valuable feature of GitLab is the ability to upload scripts and make changes when needed and then reupload them. Additionally, the solution is user-friendly."
"The SaaS setup is impressive, and it has DAST solutioning."
"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 feature is its ability to connect with different tools and technologies."
"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 simplicity of Jenkins and the evolving ecosystem of Jenkins are most valuable. Today, you do not have to write a pipeline from scratch. The library functionality of Jenkins helps you to bring all those in ready-made, and you also get the best practices for them. That is a great feature of Jenkins, and that is why it is being used significantly."
"Different types of jobs, such as Pipeline, Build, Freestyle, Maven, etc."
"The most valuable features of Jenkins are the integration of automatic scripts for testing and the user's ability to use any script."
"Jenkins is stable, user-friendly, and helps with continuous integration. As of today, I can't see any tool that's better than Jenkins."
"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."
"Integration with Microsoft Azure is one area for improvement. Azure is growing in its user base, and supports various cloud infrastructure components such as Service Fabric, App Service, etc. Some of Azure’s deployment models (like Kudu) require a steep learning curve, but if CircleCI would come up with such features (deployment to App Service) out of the box, it would be amazing."
"Billing is a mess."
"The solution’s pricing could be better."
"There needs to be some improvement in the user interface of CircleCI."
"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."
"This solution could be improved by adding modifications such as slack notifications."
"GitLab would be improved with the addition of templates for deployment on local PCs."
"The solution could improve by providing more integration into the CI/CD pipeline, an autocomplete search tool, and more supporting documentation."
"It should be used by a larger number of people. They should raise awareness."
"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."
"GitLab's UI could be improved."
"I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities."
"Better and easy-to-use integration with Docker would be an improvement."
"It would be helpful if they had a bit more interactive UI."
"The bug fix speed is very slow."
"I would like to see even more integrations included in the next release."
"Upgrading and maintaining plugins can be painful, as sometimes upgrading a plugin can break functionality of another plugin that a job is dependent on."
"We cannot change the ownership of any directory or file or any kind of directory."
"Jenkins could improve by allowing more scripting languages. We need to use Groovy scripting and it is difficult to debug and it is not ideal for creating file scripts. We tried to search for assistance but we did not find much help."
"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."