153 GitLab Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • “The goal is to achieve a high level of performance and quality, of course, and deliver Agile projects that provide exceptional business standards for users."

  • "You do not need any tools other than your browser in order to contribute, and not just in our module ecosystem, but even to Drupal core itself. That was not possible in our project prior to the move to GitLab, and that's a really big deal."

  • "Standardizing our processes would make us more predictable and efficient, freeing up engineering resources to focus on innovation rather than coordination — better for both our teams and customers."

  • “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 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 …

  • “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 …

  • “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 …