"GitLab offers a good interface for doing code reviews between two colleagues."
"GitLab is very useful for pipelines, continuous integration, and continuous deployment. It is also stable."
"We like that we can have an all-encompassing product and don't have to implement different solutions."
"I have had no problem with the stability of the solution."
"I like that it's easy to deploy our services over GitLab. The customer support is also good with a really active community. You have a lot of support that you can get online with your stack. That is probably one of the benefits of using GitLab. It's also really fast."
"It speeds up our development, it's faster, safer, and more convenient."
"Everything is easy to configure and easy to work with."
"The best thing is that as the developers work on separate tasks, all of the code goes there and the other team members don't have to wait on each other to finish."
"It is saving time for developers, which is saving money for the company."
"Reporting could be improved."
"It would be really good if they integrated more features in application security."
"I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors."
"It would be better if there weren't any outages. There are occasions where we usually see a lot of outages using GitLab. It happens at least once a week or something like that. Whatever pipelines you're running, to check the logs, you need to have a different set of tools like Argus or something like that. If you have pipelines running on GitLab, you need a separate service deployed to view the logs, which is kind of a pain. If the logs can be used conveniently on GitLab, that would be definitely helpful. I'm not talking about the CI/CD pipelines but the back-end services and microservices deployed over GitLab. To view the logs for those microservices, you need to have separate log viewers, which is kind of a pain."
"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."
"It should be used by a larger number of people. They should raise awareness."
"I would like to see better integration with project management tools such as Jira."
"It can be free for commercial use."
"Stability could be improved. I don't know the reason for the instability because there are no logs that help me to understand the problem."
GitLab is ranked 1st in Build Automation with 16 reviews while Incredibuild is ranked 12th in Build Automation with 1 review. GitLab is rated 8.2, while Incredibuild is rated 8.0. The top reviewer of GitLab writes "Provides or mandates quantitative code into the Master". On the other hand, the top reviewer of Incredibuild writes "Saves time for developers, which saves money for the company". GitLab is most compared with Microsoft Azure DevOps, TeamCity, Tekton, Sonatype Nexus Lifecycle and GoCD, whereas Incredibuild is most compared with Jenkins and Bamboo.
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.
