Obligatory: My statements are my own and do not reflect the opinions of my employer. I'm not going to name that employer, but let's be honest, I can't stop you from figuring it out if you really want.
> Are there any big shops that have converted to 100% (or almost 100%) GitLab?
We use a combination of GitHub, GitLab, and Azure DevOps across the various SW Eng orgs in our company.
On GH, we split across both GitHub.com and internal GitHub Enterprise instances. There's been some shift to put everything on GH.com, but GH Actions for private repos are kind of busted, and it's really causing us problems. Staying on GHE is less painful for some of our orgs. Some teams use Jenkins instead of Actions, which is, as the kids say, "a whole mood".
Our GitLab-using orgs generally have tighter CD integration. As much as I prefer the GH UX, I have to admit GL has a much smaller gap between "I have an idea" and "my implementation is now CI-ed, CD-ed, and published to Artifactory".
Our ADO using orgs have an even smaller gap. Seriously. If you've never used ADO, you'd be impressed by how easy it is to get a full build pipeline set up in minutes. That is, as long as you stay on the garden path. These teams also have the hardest struggles when they stray off the path. (But my intuition here is that this isn't definitively an ADO problem and might actually come down to the skill sets of those teams.)
All told, we're several hundred engineers across these solutions. By my rough count, the total number using GitLab may be a hundred or so. They really like it, and it suits them very well.
(And before anyone says "omg why do you have so many solutions", the Eng efforts at our company are thoroughly distributed instead of consolidated. And, at least at an executive level, there's currently more faith in "right tool for the job" than in "alignment". For now.)
> Are there any big shops that have converted to 100% (or almost 100%) GitLab?
We use a combination of GitHub, GitLab, and Azure DevOps across the various SW Eng orgs in our company.
On GH, we split across both GitHub.com and internal GitHub Enterprise instances. There's been some shift to put everything on GH.com, but GH Actions for private repos are kind of busted, and it's really causing us problems. Staying on GHE is less painful for some of our orgs. Some teams use Jenkins instead of Actions, which is, as the kids say, "a whole mood".
Our GitLab-using orgs generally have tighter CD integration. As much as I prefer the GH UX, I have to admit GL has a much smaller gap between "I have an idea" and "my implementation is now CI-ed, CD-ed, and published to Artifactory".
Our ADO using orgs have an even smaller gap. Seriously. If you've never used ADO, you'd be impressed by how easy it is to get a full build pipeline set up in minutes. That is, as long as you stay on the garden path. These teams also have the hardest struggles when they stray off the path. (But my intuition here is that this isn't definitively an ADO problem and might actually come down to the skill sets of those teams.)
All told, we're several hundred engineers across these solutions. By my rough count, the total number using GitLab may be a hundred or so. They really like it, and it suits them very well.
(And before anyone says "omg why do you have so many solutions", the Eng efforts at our company are thoroughly distributed instead of consolidated. And, at least at an executive level, there's currently more faith in "right tool for the job" than in "alignment". For now.)