"Everything is easy to configure and easy to work with."
"The stability is good."
"This product is always evolving, and they listen to the customers."
"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."
"GitLab integrates well with other platforms."
"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."
"CI/CD is very good. The version control system is also good. These are the two features that we use."
"Good reporting functionalities."
"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."
"I would like more Agile features in the Premium version. The Premium version should have all Agile features that exist in the Ultimate version. IBM AOM has a complete Agile implementation, but in GitLab, you only have these features if you buy the Ultimate version. It would be good if we can use these in the Premium version."
"Reporting could be improved."
"I would like to see better integration with project management tools such as Jira."
"In the free version, when a merge request is raised, there is no way to enforce certain rules. We can't enforce that this merge request must be reviewed or approved by two or three people in the team before it is pushed to the master branch. That's why we are exploring using some agents."
"The solution could improve by providing more integration into the CI/CD pipeline, an autocomplete search tool, and more supporting documentation."
"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."
"We would like to generate document pages from the sources."
"Lacks deeper reporting, the ability to compare things."
Enjoy a free DevOps platform cloud subscription
GitLab is ranked 3rd in Software Composition Analysis (SCA) with 18 reviews while JFrog Xray is ranked 8th in Software Composition Analysis (SCA) with 1 review. GitLab is rated 8.2, while JFrog Xray 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 JFrog Xray writes "Stable, scalable and offers great reporting functionalities". GitLab is most compared with Microsoft Azure DevOps, TeamCity, Tekton, Sonatype Nexus Lifecycle and AWS CodePipeline, whereas JFrog Xray is most compared with Black Duck, Snyk, Sonatype Nexus Lifecycle and Fortify Static Code Analyzer.
See our list of best Software Composition Analysis (SCA) vendors.
We monitor all Software Composition Analysis (SCA) 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.
