"A user friendly solution."
"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."
"GitLab offers a good interface for doing code reviews between two colleagues."
"The most valuable features of Gitlab are integration with CIE and the ability to rapidly deploy solutions, projects, and applications. It is very easy to use, and there are no complaints."
"Everything is easy to configure and easy to work with."
"We like that we can have an all-encompassing product and don't have to implement different solutions."
"We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people."
"This product is always evolving, and they listen to the customers."
"Our customers use it to check for unauthorized file transfer."
"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."
"It would be really good if they integrated more features in application security."
"It should be used by a larger number of people. They should raise awareness."
"The only thing our company is really waiting on in terms of features is the development of metrics."
"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."
"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."
"We would like to generate document pages from the sources."
"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."
"I would also like to see updates on a more frequent schedule."
Earn 20 points
GitLab is ranked 5th in Application Security Testing (AST) with 16 reviews while Spirent CyberFlood is ranked 22nd in Application Security Testing (AST) with 1 review. GitLab is rated 8.2, while Spirent CyberFlood is rated 0.0. The top reviewer of GitLab writes "Provides or mandates quantitative code into the Master". On the other hand, the top reviewer of Spirent CyberFlood writes "Analyzes network security or even existing processes". GitLab is most compared with Microsoft Azure DevOps, TeamCity, Tekton, Sonatype Nexus Lifecycle and GoCD, whereas Spirent CyberFlood is most compared with Ixia BreakingPoint, Ixia BreakingPoint VE and Acunetix by Invicti.
See our list of best Application Security Testing (AST) vendors.
We monitor all Application Security Testing (AST) 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.
