With more than 100,000 organizations self-hosting GitLab, we have the largest share of companies who choose to host their own code. We’re estimated to have two-thirds of the single tenant market. When Bitrise surveyed ten thousand developers who build apps regularly on their platform, they found that 67 percent of self-hosted apps prefer GitLab’s on-premise solution.
Similarly, in their survey of roughly one thousand development teams, BuddyBuild found that 79% of mobile developers who host their own code have chosen GitLab:
In their articles, both Bitrise and BuddyBuild note that few organizations use self-hosted instances. We think there is a selection effect since both of them are SaaS-only offerings.
Based on our experience, the vast majority of enterprises (organizations with over 5000 IT + TEDD employees) self host their source code server (frequently on a cloud service like AWS or GCP) instead of using a SaaS service.
Another assumption is that git is the most popular version control technology for the enterprise. Certainly now every enterprise has switched (completely) yet but it does seem that git is almost 10 times larger than SVN and Mercurial.
Our commitment to seamless integration extends to CI. Integrated CI/CD is both more time and resource efficient than a set of distinct tools, and allows developers greater control over their build pipeline, so they can spot issues early and address them at a relatively low cost. Tighter integration between different stages of the development process makes it easier to cross-reference code, tests, and deployments while discussing them, allowing you to see the full context and iterate much more rapidly. We've heard from customers like Ticketmaster that adopting GitLab CI can transform the entire software development lifecycle (SDLC), in their case helping the Ticketmaster mobile development team deliver on the longstanding goal of weekly releases. As more and more companies look to embrace CI as part of their development methodology, having CI fully integrated into their overall SDLC solution will ensure these companies are able to realize the full potential of CI. You can read more about the benefits of integrated CI in our white paper, Scaling Continuous Integration.
In his post on building Heroku CI, Heroku’s Ike DeLorenzo noted that GitLab CI is “clearly the biggest mover in activity on Stack Overflow,” with more popularity than both Travis CI and Circle CI:
While the use of Jenkins for CI is still higher than any other solution, we see more and more organizations moving from Jenkins, because upgrading their Jenkins server is a brittle process. The last two big things that GitLab CI lacked were scheduled builds (contributed to GitLab 9.2) and cross-project builds (released in GitLab 9.3 on June 22).
When people first hear about a new product they frequently ask if it is any good. A Hacker News user remarked: 'Note to self: Starting immediately, all raganwald projects will have a “Is it any good?” section in the readme, and the answer shall be “yes."'. We took inspiration from that and added it to the GitLab readme. This page continues that tradition.