130 GitLab Testimonials

“With GitLab and Kubernetes, I can have three deploys a day — unlike the classic release cycle of every three months. I know from my steps that the test has passed, and I can promote automatically from staging to production directly in GitLab.”

“GitLab has made group work easier it was a crucial tool in multiple group work projects. Really helped with coordinating development."

“With our old code testing tool, we had to provision to our maximum. So if we ever needed to run 50 concurrent tests, we were forced to pay for 50 all day, every day. Our cost was approximately $50 per concurrent test per month for 50 concurrent tests, even though outside of our core business hours the tests were rarely needed to that magnitude."

“We had developers that thought, Why would we do something else? Jenkins is fine. But I think those people need to see GitLab first and see what the difference is because GitLab is so much more than Jenkins. The power of GitLab is you can do so much more and you can make everything so much easier to manage.”

“We are just replacing these outdated tools bit by bit, doing it the agile way. We really wanted to replace Jenkins and immediately we saw that Stash was the first one to replace because it was logical to also host your Git repositories in GitLab, and now we have started looking at other tools (f.i. XL Deploy, Nexus) that we can replace with GitLab.”

“One tool for SCM+CI/CD was a big initial win. Now wrapping security scans into that tool as well has already increased our visibility into security vulnerabilities. The integrated Docker registry has also been very helpful for us. Issue/Product management features let everyone operate in the same space regardless of role.”

“I would say my first three months the cloud team was shifted to entirely GitLab. It was a good investment because GitLab is now running and I don’t need to take care of it anymore.”

“GitLab has been great for us. It is a good kind of a software that we love.”

“As GitLab reported new capabilities, we were able to learn about them and then choose which one we would pick and choose to put into action for the rest of the teams.”

“GitLab has had a positive effect on our culture. Everyone feels better about shipping code and deployments. There is more confidence in the org and deployment is a non-issue.”

“The managers are excited (about GitLab) because it helps reduce the amount of time we spend on things that we don’t need to be spending time on. Focusing on the important stuff basically, get back to actually engineering and not focusing on building weird pipelines with Jenkins and Shippable and GitHub and trying to hook everything together in crazy scripts and stuff.”

“Just having the real scalable architecture of GitLab, how every piece is independently scalable was good for us because we [the team] are all scalability nerds. So, looking at that architecture, we can say, ‘Oh my god, it’s sane architecture."

“The GitLab migration in general is one of our largest successes. Of the primary implementations that Site Reliability Engineering has brought to engineering at KnowBe4, the choice to move the department to GitLab ranks up there as one of the best.”

“The communication between 100 versus 18 people is incredibly different. There’s a lot more information now. So I think that there’s an element of trying to make sure that we have the information available to the team as they need it, but without drowning everybody in information which is, at points, irrelevant.”

“GitLab made it easier for all developers to work with CI/CD pipelines, making the process of bootstrapping a new service much more transparent and approachable and removing the DevOps/SRE team as a bottleneck.”