I'm a product owner. So, I'm not really using the product myself on a day-to-day basis, but I've been managing teams and companies using GitLab for four to five years. Besides that, I've been involved in two or three tool selection experiences where GitLab was one of the candidates, and because of that, I pretty thoroughly investigated GitLab.

In some of the projects we are involved with, we use GitLab for the purposes of issue management and as a configuration management tool. Along with GitLab, we also use the core Jira software for issue management functionality, as well as GitLab Runner for its CI/CD tools.

Our internet connection runs on a different infrastructure to the greater internet system, so we are using on-premises versions of all these solutions. Because nothing is cloud-based, we don't need much in the way of firewall or security solutions.

We primarily use GitLab for code migration and version management. It helps us maintain metadata, manage versions, and facilitate continuous integration when working in teams. When working on a feature, we create a feature branch, which allows us to work on the feature independently. Once the feature is complete, it must be merged into the main branch. This streamlines the process of deploying the application to the production environment.

Our primary use case is for source code maintenance, then doing the build and running code coverage tools like SonarQube, and then deployment.

GitLab is a solution for source code management, container registry, pipelines, testing, and deployment.

We are using GitLab for team collaboration, code management, and certain CICD pipelines.

I use GitLab to manage repository code sources, scanning code sources, and CI/CD. We have around 100 users.

I use the tool for deployment. 

I use GitLab for some of my CyberArk scripting work.

Our company uses the solution as a repository manager for our best code, to set up CI/CD pipelines, and to build projects and get architects. We build code and generate artifacts that we push to UrbanCode for deployment. 

For one use case, we created an entire CI/CD pipeline that deploys code to the artifact and Target Server. This deployment was our first using the solution and included a lot of scripting. The customer has 250 current users that includes maintenance, owners, and developers.

Eventually, we plan to use the solution for all deployments. 

We use the solution for on-premises repository management

There are two primary functions. The first function is a Git-compliant source code repository, and the second function is a full-fledged CI/CD platform.

GitLab was mostly used for version control. All of the code was uploaded into GitLab and then shared across the company. We also used it for running CICD pipelines and automating those pipelines.

We create the pipeline and push it to GitLab to initiate the process. The cloud integration is straightforward.

I primarily use it for verifying some things. We're using it as a repository. It's used for software code. 

We have our CI/CD pipelines set up in GitLab. It is our code base. 

It is used for saving source code, and then people get the source code out of it, make a branch, and merge it to make a big file for deployment. So it's mainly a source code deployment tool.

GitLab is for professional teams, and it has some abilities in the user interface that are interesting to me. 

We are using GitLab for code management. We put code onto their servers. This allows developers to have a centralized place for code collaboration.

I've used the solution just for my learning purposes. My company is using currently GitLab. We are using it for our CI/CD purposes for continuous integration and continuous deployment.

My company's programmers use GitLab for everyday development purposes.

My primary use case is for creating pipelines and automation workflows.

Our company is a partner and installs the solution for clients who manage their ACD and DevOps pipelines. 

We have 700 developers who use the solution, Microsoft's integration, and SharePoint for uploading. 

During the development environment, we have a different number of developers, close to five. So each of them will have a different project. Maybe some of them do it in one project, but their assignment or the activity they are doing may be different, so they will do their activity and then they will push it to the GitLab. If there is an amendment or update required, they will pull it from GitLab and if they do their activity again, they will push it. 

We use it for version control and CI/CD.

We are using it for pipelines, continuous integration, and continuous deployment. 

In terms of deployment, it can be a cloud solution, but we have installed it on our site on Azure.

We are providing solutions for consumer electronics. We have a repository of our code between the device team, mobile applications team, and cloud team.

We primarily use this solution for end-to-end CI/CD solutioning and deployment as well as infrastructure, architect and environmental management. In addition, we plan to use it for version control and SaaS solutioning and have heard it is great.

The primary use of the solution is for LCDs and as a repository.

My team primarily uses GitLab for CI/CD purposes. Whatever code I develop has to go with the team, so I work in a team that tries to write its version of the code, or uses the ticketing system, takes a ticket, covers that information, and then updates the main branch about it. That's the use case my team has for GitLab.

The solution is cloud-based. There are around 30 people using this solution in my organization. 

We use GitLab as a source code repository, terraform modules repository, generic packages repository and for our CI/CD pipelines.

We use GitLab for all of our Git sources and it is mapped to our integrated solution for the complete ICG platform.

We are using the product for configuration management and source course management. For some projects, we are using it issue management.

We have a normal use case to build source code and our agenda and then try to deploy it. The deployment is not specifically automated, it is semi-automated. So it is normal. We create an artifact, try to build it, and then deploy it onto the application server. It's not fully automated. 

I'm part of the application development team comprising 10-12 developers and I have used GitLab for configuration and version management. We have also used it for DevOps, but I have not been involved in the DevOps side. My work with GitLab involved basic version management (i.e. checking in, checking out, merging) and related features. 

I have also used GitLab for doing remote builds, which is when you check in and it triggers the build on the application remotely. For example, we have a YAML script that has been written for performing builds on GitLab automatically and when that script gets executed, it performs the builds and copies them to the destination folder. All of this gets triggered from GitLab.

I work in PMO, and I standardize the workflows for scrum teams, AI teams, and kanban teams. If I have some scripting in Jira, and I need to save it in GitLab.

It is our source-code repository. It's used for the BI process, continuous integration, and continuous development. It's used for DevOps people. All of our IT people use GitLab.

GitLab is used for pipeline development, automation, and deployment.

Our primary use case is for source management.

Our company uses the solution to manage code, Wiki, and repository management for multiple projects on Truck It In. The solution helps us manage our experience with projects. We currently have twenty-two developers using the solution.  

We are in the process of executing the pipelines to use the solution for CI/CD. 

We use this solution for source code management, and also team collaboration for the application lifecycle.

We use Gitlab for CICD work. 

Because GitLab uses an education license for cloud, there is unlimited storage for each account, so it's very useful. It is very flexible and easy because you can store data on cloud.

I am using GitLab for many purposes, such as CI/CD.

We are using it for building mobile applications and web applications. I am supporting the code in GitLab. It is only for giving access to my development team, and I just see what merge requests are coming.

We are using this solution for DevOps adoption primarily.

GitLab is being used as a repository for our codebase and it is a one stop DevOps tool we use in our team.

I primarily use GitLab for maintenance and deployment of projects.

We use this solution for storing repositories for distributed programming. We have 15 to 20 users. We generally keep our POC repositories on GitLab.

GitLab can be deployed on-premise and in the cloud.

GitLab is mainly used as a repository.

GitLab can be deployed on-premise and in the cloud and it is used for DevOps.

We were working on our pipeline infrastructure running GitLab and we needed some scripts, such as Terraform, to complete some operations.

My daily usage involves fetching code, creating branches, modifying the code, and then committing my changes. Once I'm ready for a review with my colleagues, I create a merge request. Then, during a code review, they will use the interface to write comments. Once everything in the comments has been addressed, I complete the merge. This describes a typical scenario.

We develop under Linux.

GitLab is a platform that facilitates hosting, collaboration and version control. We also make use of its pipeline capabilities. 

We are using GitLab for managing our code. We have created branches and posted code, and as our team members complete assignments, the code is pushed to there.

I am using GitLab for code management, such as code cloning, and code-to-data.

I use GitLab to bring code from repositories.

We use GitLab for the continuous deployment of CI/CD pipelines that are running on various GitLab services. We also use it to run nightly jobs and to run any other case-specific issues.

We used the solution for keeping Yama code files there for our project.

We are a startup company working on a new firewall product, and we use GitLab as part of the software development process.

We are a consultancy company, and we mostly sell application tools such as Jira and Bitbucket, but sometimes, our clients have Gitlab or Github, and then we offer the consultancy experience in DevOps for improving the process.

All use cases for this solution are for the financial industry. Around 50% of our clients are financial services.

We primarily use this solution for repository tracking issues and reporting. We also use it for component integration. Our focus is pipeline field leads. We used to work with JIRA. I'm a developer and we are customers of GitLab.