TrustRadius Insights for GitLab are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Cloud-Based UI and Git Integration: Users have praised the cloud-based UI of GitLab for supporting Git version control, allowing local checkout, and enabling multiple developers to work simultaneously in one file. The reduction of code conflicts and enhanced collaboration are highlighted benefits of this feature.
Integration Features: Reviewers highly value the integration of GitLab with version control, code review, and project management features. They find it easy to configure GitLab runners for running tests and defining permissions using Terraform, which streamlines their development processes effectively.
CI/CD Capabilities: Users find the CI/CD pipelines, merge requests, and open-source nature of GitLab beneficial for their development workflows. They appreciate the platform's integrations with other tools such as Jira, Azure DevOps, and Toad. Additionally, they praise its security features for ensuring a safe software deployment environment.
In our organization, I work as development team member, I have to manage different code bases with a team of individuals. In that process, there are certain parameters for code reviews and quality checks for deliverables GitLab helps in implementing CI/CD pipeline for an efficient way to create deliverables it also provides shared and instance-based runners.
Pros
CI/CD pipeline implementation
AI tools for code review
Version control of source code
Privacy parameter implementation
Cons
UI refresh takes time
Limited feature on the general tier
CI/CD additional scripting
Likelihood to Recommend
I am working on multiple automation plugins based on dotnet framework, i have to create deliverables as executable for the client , features from GitLab like AI tool to check sensitive information like environment variables and hashes don't get pushed on to the branches also it helps in maintaining a check on versions of dlls which helps the code reviewer to maintain code structure and nomenclature. Sometimes UI updating is not accurate but it can be neglected.
VU
Verified User
Engineer in Engineering (Architecture & Planning company, 51-200 employees)
We use GitLab mainly for code hosting, CI/CD, and issue tracking. It helps us in keeping development organised, automating deployments, and making collaboration easy. Our scope is pretty standard: managing source code, running tests, deploying services, and tracking bugs/features all in one place. We also use it for a few non-technology projects (but for people who are in close collaboration with the engineering team).
Pros
CI/CD
Source code hosting
Visualisation of test results
Merge requests
Cons
Access roles
Wiki pages editor
Likelihood to Recommend
I'm very likely to recommend it as all-in-one platform for software development projects. It really does the job. I will also put a disclaimer that it's not perfect (mainly in the UX). But it is very straightforward in many aspects, which is great
GitLab is our CI/CD platform of choice, which we use to manage our code, product builds and deployments in an automated way. It's very powerful and it allows us to define custom pipelines in YAML files that we can put under version control in the platform itself. It supports every Git functionality that any company, big or small, would need to store code, environment variables, review merge requests, resolve merge conflicts and handle merges from multiple users. In summary, it's a very powerful all-in-one platform.
Pros
Define CI/CD pipelines as code
Store your code
Allow merge request reviews
Store secrets as environment variables
Cons
The free version was a bit slow
Likelihood to Recommend
It's a complete solution to store your code, perform code reviews and automate your builds and deployments through automation. Pipelines defined with YAML files are especially useful and powerful. Any company, regardless of the size of the team or the project would find it extremely helpful. Secrets used by the build agents can also be stored in the platform itseld as environment variables.
GitLab has been great serving as a foundation to manage our source code. The team has been able to create and manage repository with version control and branching that has resolved a bunch of prior issues with the code merge, especially given the different teams that collaborate on the same code
Pros
Robust Git repository management
CI/CD Pipeline
Security and Vulnerability Scanning
Cons
UI can use some improvements and takes quite getting used to
Slow at times
Finding stuff for troubleshooting can be a bit difficult
Likelihood to Recommend
Great for collaborating and managing the git repository. Especially when you have several teams sharing the environments and having a different release schedule.
VU
Verified User
Manager in Engineering (Banking company, 10,001+ employees)
My organization is using git for the source code management like pull, push, merge request and changes history. We are also using GitLab to track the issues and resolutions. Its also provide some linking with the other issues tracking tools like MantisBt, Jira, Trello etc. It has options to connect with jenkin and other build creation tools, That helps allot at the time of QA and UAT.
Pros
Source code management
Issues tracking and linking with commits
Intigration with build creation tools and deveopes
Proper documentation of the features and operations
Cons
Some time its taking time in loading
Can improve the UI part
Graph view of commits is littlebit confusing in case of number of branches, It can be little bit improve
Likelihood to Recommend
If some one wants to work with a very high quality and relible platform then they should use GitLab, It can auto merge the source codes without any harmfull action. All the codes and condition will be there. Its very helpfull in case of morethen one developer in a team and all are working on the same file or project.
Gitlab is a platform used for collaborative work on multiple files. We use this product to address the same. It can also be integrated with existing infrastructure to provide seamless service and integration. The scope is limited to multi user collaborations so that individual workers can work independently and have version control.
Pros
version control
multi user collaboration
ease of use and integration
Cons
tokenisation
reduced downtime
frequent bugs
Likelihood to Recommend
It is most appropriate in use case where multi user collaborative work is required. If there is use case to integrate with tools and scripts then it can be easily done. Due to bugs in tokenisation, it sometimes lead to bugs and breaks during a typical workflow. Setup can be made easier as well.
VU
Verified User
Engineer in Engineering (Semiconductors company, 10,001+ employees)
We use Gitlab to track issues by project, whether Terraform IaC projects, Node JS projects, Jupyter Notebook data analysis products, or custom in-house Python packages. We also use it to monitor our projects' security posture to ensure no vulnerabilities go unchecked. It helps our small cross-functional team collaborate.
Pros
Version Tracking.
Diff analysis between revisions.
CI/CD Pipeline Creation and Maintenance.
Cons
More templates for common project use cases.
Ability to track vulnerabilities on a specific branch, instead of just the default one.
Likelihood to Recommend
It is well-suited for any project that needs VCS. It's an excellent choice for teams that might be remote or have to collaborate across teams. Plenty of features allow for async working. With its dashboards and reporting features, it is also suitable for nontechnical PMs or stakeholders. It allows for very bespoke customization and can most often do much more than you need it to.
I use GitLab daily for my development-related activities, including CI/CD pipelines. We maintain all internal projects on GitLab, and it helps multiple developers collaborate on the same project. As a developer, I appreciate the user-friendly Pull Request feature on GitLab.
Pros
GitLab helps developers collaborate including planning, source code management and compliance
GitLab helps projects to build continuous integration and maintain a continuous delivery pipeline.
Gitlab help developers to store artifacts
Cons
Gitlab can provide GenAI code review feature
Gitlab can provide security mitigation using GenAI
Gitlab can provide recent changes feed like github
Likelihood to Recommend
For me, I'm utilizing GitLab for internal project development and collaboration
within my organization, while primarily utilizing GitHub for public or
open-source projects.
We use GitLab to store and manage the codebase of our organization. We have multiple projects in there but they are all part of the same platform. We do the code review in GitLab.
We also have integrated CI/CD and debugging tools, like Argo Workflows, and Grafana. We also use the integration with Jira and Slack.
Pros
CI/CD integration
Customizable approver privilege
Merge Request dependencies
Auto-merge when pipelines pass and code is approved
Cons
GitLab Code Suggestions is very poor compared to GitHub Copilot. The company decided to use Copilot instead because the GitLab one is slow and the recommendations are very basic.
Some merge requests display changes in code that has not been touched because there is a merge commit even if the changes are already in the target branch.
Sometimes it requires approval when it is not needed, but this is likely caused by the same issue of the merge commit.
When pasting a piece of text that was copied from a suggestion in the GitLab comments during code review, the text is also formatted in a code suggestion, despite there is already a suggestion in the comment.
Likelihood to Recommend
The DevOps people in the company have configured our GitLab account very well, so it is well integrated with other tools and help us with our CI/CD process. It validates that the code is already merged in the lower branches and requires approval according to some configurations. Some things are customized but GitLab allows you to do it.
