GitLab Reviews and Ratings

Use Cases and Deployment Scope

I have used GitLab previously in one of the team project. The built in CI/CD pipeline feature helps a lot where we don't have to worry about deploying the code manually after every change pushed to the repository. The interface was user friendly. One thing that sets GitLab apart is the graph visualization of the milestones completed.

Likelihood to Recommend

It is well suited for the projects where you have to deploy in various environments like dev, qa or production. Once a CI/CD pipelines has been created, one can simply push their code by raising a PR from one env to other and deploy theier code to the targeted environment.

Use Cases and Deployment Scope

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.

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.

Use Cases and Deployment Scope

We use GitLab to manage our source control and visualize our branches , resolved merges/conflicts , and conduct code reviews. In these functions we find that GitLab provides a robust way to view and manage.

Likelihood to Recommend

Gitlab has been useful in a number of situations, but we frequently use it to help enforce multiple levels of code checks and approvals before any code is merged into a branch. Some other scenarios would include handling conflicts and pushing code to a different branch.

Use Cases and Deployment Scope

We use GitLab to as our version control solution. We have multiple Git repositories that are store in GitLab. Furthermore, we use GitLab to branch and merge project branches. We are able to effectively collaborate any changes we make through GitLab. Finally, GitLab allows us to centralize our code base and makes it much easier to maintain our "source of truth".

Likelihood to Recommend

GitLab self-hosted solution is well suited for organization that have strict security policies that prohibit company information from leaving the company networks. By self-hosting GitLab, all traffic remains internal to the company. It's also well suited for small to medium sized departments that need an open-source version-control software. It's easy to use and setup, and most administrator can deploy it without much hassle.

Use Cases and Deployment Scope

Our organization utilizes GitLab Enterprise to host all source code across frontend, backend, and infrastructure teams and to achieve continuous deployment and continuous integration processes in a fast-paced E-Commerce environment. Development teams use the code review feature to ensure quality and standards across teams and individual contributors. Integrations with a variety of tools allow for cybersecurity use cases such as automatically scanning security issues in the source code while it is still being developed.

Likelihood to Recommend

GitLab with the Enterprise plan is well-suited for large organizations that can benefit from the vast range of included features and have the resources to support custom CI/CD pipelines and policies with their own infrastructure and dedicated DevOps resources. They also might value the ability to self-host it.

Companies of small to mid size that mainly develop mobile applications are probably better (and cheaper off) with a different platform for source code hosting and a dedicated Mobile CI/CD platform like Bitrise.io. The complexity may be overwhelming for smaller teams or individuals with limited experience in version control systems, leading to potential inefficiencies and difficulties in adoption.

Use Cases and Deployment Scope

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.

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.

Use Cases and Deployment Scope

We use GitLab for everything code from source control to CI/CD. In our area of business, we develop complete software solutions for both mobile and web, both frontend and backend.

GitLab is the best user experience for our teams of developer and we can see how much the tool is appreciated when comparing it to competitor products.

Likelihood to Recommend

GitLab is good if you work a lot with code and do complex repository actions. It gives you a very good overview of what were the states of your branches and the files in them at different stages in time.

It's also way easier and more efficient to write pipelines for CI\CD. It's easier to read and it's easier to write them.

It takes fewer clicks to achieve the same things with GitLab than it does for competitor products.

Use Cases and Deployment Scope

As a VBA (Visual Basic for Applications) programmer, I use GitLab to post various code snippets or projects related to my developed programs. GitLab provides a centralized location to house all of these snippets which allows for quick/easy access for all future builds without having to sift through notes or folders. Additionally, code formatting provides ease of visualization.

Likelihood to Recommend

GitLab is perfect for programmers who need to store their own code snippets without having to save individual text files or keep notes within various note applications. Also, for languages other than VBA, GitLab has excellent version control.

Use Cases and Deployment Scope

We compare gitlab and github and the scope is stay at evaluation stage. We will use GitLab if the evaluation is approved by the top leader of my organization. The main use case to use GitLab are for Source Code Management (SCM). I had tremendous amount of different computer programming languages. So the most important features is how to do hot deployment without manual intervention. The other use case is to do continuous Integration/Continuous Deployment (CI/CD), so we can design the pipeline to detect the software errors created by developer in advance. These two uses cases are the most critical for our business.

Likelihood to Recommend

I would rate Gitlab 9/10. The reason I gave this high ranking is because Gitlab is All-in-One platform. I just listed two use cases from prior survey question, the SCM and CI/CD are the most important features for our business and GitLab extensive features set makes our code reviews and issue tracking more collaborative between team members and different organization.

Use Cases and Deployment Scope

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.

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.