130 GitLab Testimonials

"That was the main goal that we had - to reunify multiple tools into a single one and make it really easy for developers to deploy to production. We were at 10 per day before the migration. Now with GitLab, we do 50 deployments per day in production, which is way more efficient than when we had to switch between GitLab and Jenkins."

“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.”

“We wanted to bring a tool on to our own premises so that we have it under our control, and also have it in real time. That was really a big step forward.”

“GitLab met our requirements and gave us the best value for the price. The feature set with GitLab on-premise was more advanced than GitHub and we saw the pace and development [of GitLab] moving faster with a community that was active in delivering and contributing.”

“Before we had our build pipeline running with Jenkins So, we have a develop, release, and master branch, which is finally released to the public. Every time you build a branch of those three, the outcome would have been installs on several VMs and then our test automation started in a separate process. At the end of the process you got an email that it worked, it didn’t work, where it failed, and stuff like that.”

“A lot of people used Git at the company and just knew that it was faster, better, and what everybody else is using nowadays. It’s also harder now to train somebody to use Mercurial because Git is so prevalent. So, when you hire a developer, they probably know Git but they may not know Mercurial.”

“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.”

"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."

“When someone makes a commit on a CoreDNS repo and they want to do a deployment, we need to be able to pin a specific environment with exactly which type of cluster CoreDNS is going to be deployed to. The environment specific variables allows us to go out and do that.”

“It’s good to make this transition in terms of our image because it shows the community that we are providing cutting-edge technology.”

"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."

"Over the past two years, GitLab has been transformational for our organization here at UW. Your platform is fantastic."

"We had more than 2,000 projects in a few months, a very fast adoption rate compared to our other code hosting platforms.”

“The integration fluidly transfers Bugsee data into a GitLab issue so that everything that is ever needed to diagnose a crash is given directly to an engineer.”

“Gerrit would always have, essentially, just one single commit at a time that was being amended on each change. That worked great for dinosaurs like myself who like a pristine linear commit history where each commit pushed is fully functional. An equally valid option championed by those who cut their teeth on the GitHub model is to iterate and push multiple commits together, dead-ends and all, via a single merge request.”