What is your primary use case for GitLab?

GitLab is predominantly used for software development and practicing DevOps. GitLab CI/CD is one of the best features, and the solution is used primarily for software development.

We use the solution as a source code manager or version control manager.

I use the tool for deployment.

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

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

We use the solution for on-premises repository management

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

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.

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

We are using this solution for DevOps adoption primarily.

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

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

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.

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.

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.

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

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

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

I use GitLab to bring code from repositories.

GitLab can be deployed on-premise and in the cloud. GitLab is mainly used as a repository.

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

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.

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

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.

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.

We use it for version control and CI/CD.

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

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

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 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 used the solution for keeping Yama code files there for our project.

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 providing solutions for consumer electronics. We have a repository of our code between the device team, mobile applications team, and cloud team.

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

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.

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.

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

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.

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.

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