Moving into a system like GitLab will help any organization or enterprise to get into DevOps methodology and continuously improve the deployment workflows to achieve quality, agility, and self-serviceability.

Bala Kannan, Senior Software Engineer

With GitLab, we finally had a single tool that not only aligned to divergent engineering workflows, but also allowed for meaningful continuous integration.

Bri Hatch, Director of IT

The Best Tool for CI/CD and more.

Jordan H.

GitLab has scaled to effectively host over 10,000 projects, representing roughly 400 GB of data, on one instance with the same speed and quality of the first project.

GitLab takes the culture of the community and brings it to where you can actually codify how humans can interact together well. That’s difficult to capture, and I think GitLab does a really excellent job of not forcing people but really encouraging a collaborative beneficial work environment.

Chris McClimans, Cross-Cloud CI Project Co-founder

Things were looking pretty scrappy for our CI pipeline only a few months ago. Now it is a whole different ballgame. If your team is looking for a way to breathe fresh life into a legacy CI pipeline, I suggest taking a look at GitLab CI. It has been a real game changer for our mobile team at Ticketmaster.

Jeff Kelsy, Android Developer

[With GitLab] The amount of effort involved in actually getting to the newest version that you’re supposed to be testing, whether you’re a developer or a QA engineer, is minimized immensely.” QA engineer’s tasks – about an hour a day in total – have been slashed to 30 seconds, a 120x speed increase.

Greg Campion, Senior Systems Administrator

Essentially, we look at GitLab as a building block, and we just build whatever we need on top of it. Whether it’s a wiki or a custom integration, GitLab helps create an engineering culture.

Jared Short, Director of Innovation

The significant improvement that we’ve seen is a huge increase in the visibility of what is changing in the code. It’s become easier to track what’s being changed, by whom, and for what purpose. We now have this record of all of the questions that are asked about changes in the code, why changes are made and can more easily identify mistakes.

Alexandre Lossent, Version Control Systems Service Manager, CERN IT department