GitLab Reviews

My most common use cases for GitLab are development and managing repositories, primarily focused on code development work.

The features that are really useful for my use case generally include pulling, merging, and ensuring the pipeline is upright, which are very intuitive.

It helped me personally and my team to save time and money.

In terms of impact from using GitLab as an all-in-one DevOps platform, it helped with my project development life cycle.

The broad use of GitLab is for code check-ins, but I also use it for issue management and backlog management. It has integration with testing tools as well, and I utilize those features. GitLab supports code collaboration alongside issue and backlog management. Everyone within my team or pod, as we call it, can see each other's issues. The scrum master can look at the velocity and the burn-down charts.

I find all the CICD pipelines valuable, along with the simplicity it offers developers. When comparing it, certain features available in Jira are not present. Specifically, the ability to have weights at the milestone and epic levels does not exist. However, the security features are good and restrictive.

I use GitLab to manage our development lifecycle. We use it to store code and automate our CI/CD pipeline. Once developers commit their code, the CI/CD pipeline automatically starts, supporting development through various stages. It is part of our software development life cycle.

GitLab enhances productivity and reduces time since many tasks are automated. I appreciate the team collaboration it offers, enabling multiple people to work on the same Git repository seamlessly. 

Additionally, it streamlines our DevOps processes with automated CI/CD pipelines.

We use CI/CD for producing a Docker image. Afterward, we use Argo CD with Helm for deployment on OpenShift. Initially, we had the open-source version, however, we upgraded to the Ultimate version for security scanning and other features.

The CI/CD pipeline with Helm has significantly improved deployment speed and efficiency. Before using this solution, our deployments took four to five hours. Now, we can deploy applications in ten minutes. The Ultimate version offers enhanced features for security scanning through DAST and SAST analysis, which have greatly benefitted our project workflow.

Mainly, we use GitLab as a source control repository, and I use GitLab CI for the CI/CD pipeline.

GitLab's source control is excellent. Having the source control and pipeline in the same platform makes integration seamless. It is already integrated, with no need to configure any webhooks or other settings. 

Implementing CI/CD with GitLab has accelerated the time to market significantly. As we implement automated testing and DevSecOps, it speeds up the process by forty to sixty percent.

We were using GitLab as a repository for our project. Whenever we were developing anything, we would commit our codes there. 

We used it for creating branches, merging branches, and comparing branches to resolve conflicts during code committing. We configured the CI/CD pipeline to automate our deployment process. We also utilized it in conjunction with tools like Octopus and OpenShift.

GitLab helped us streamline our code-committing and versioning process. It provided better user-friendly solutions for comparing and resolving conflicts when committing code. 

The CI/CD pipeline setup was straightforward and required fewer commands, making it simpler to use compared to Tekton. This efficiency in code management and deployment contributed to smoother operations in our projects.