Huh, I thought gogs and its forks dominated self hosted git, because it's just so easy to set up and use.
What’s Next for Gitlab CI: Auto DevOps
41–50 of 91 posts
Re: What’s Next for Gitlab CI: Auto DevOps
#42I would imagine that git dominates self-hosted git. I just have bare repos on servers I can ssh into. End of problem.
Storage (/infrastructure) is only a small part of the GitHub/GitLab functionality; with a bare repos one solves only one problem of many :-)
Re: What’s Next for Gitlab CI: Auto DevOps
#43I really like the core of gitlab. It's a really good git hosting system that is easy to maintain and work with. My self hosted instance has broken only twice in the last 1.5 years and it was always because of an upgrade and it was always easily fixed. But now i have to say i'm afraid gitlab is getting bloated. Why not keep the core product as a seperate thing from things like CI? a simple plugin style system would be…
I just updated the NixOS gitlab package from 8 to 9[0]. It was a nightmarish experience. There are 5 microservices :
- gitlab (the core)
- gitlab-sidekiq (a work queue)
- gitlab-workhorse (provides the frontend)
- gitaly (a git wrapper that caches stuff)
- gitlab-shell (a shell spawned when doing your git clone)
Those are written in either go or ruby. Sometimes mixing the two in the same repository. In the main gitlab repo, there is also some unvendored js dependencies for the frontend, necessitating to jump through some more hoops.
Gitlab has a bunch of hardcoded paths to logfiles and config files. Some config files are toml, others are yaml. Different services need different configs, sometimes duplicating the config entries in a different format.
I love gitlab as a product. But as a sysadmin, it's one of the worst thing I've ever had to deploy.
[0]: Well, it's not pulled there, but it's at https://github.com/NixOS/nixpkgs/pull/27159 if you're interested.
Re: What’s Next for Gitlab CI: Auto DevOps
#44Earlier quoted context omitted.
I work with self-hosted Gitlab daily and I’ve never thought the UI was bad or slow. In fact, I think it works pretty well. To the other commenters: Do you have any examples? Also, I’m excited about auto deployment. The less tools one needs to get software shipped, the better.
To see that the UI design is bad at times, take the design of merge requests and issues for example. On Github you can easily see what happens, comments are surrounded by a black border, the name of the comment author and the date are clearly visible and have a different background color from the comment text. Actions like closing and re-opening are distinctly different from comments and are color coded (green -> re-…
I appreciate the thoughtful and specific feedback. We are working hard to make merge requests and issues intuitive and easy to work with. Many of your observations regarding merge requests are being worked on as part of this issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/33095
Re: What’s Next for Gitlab CI: Auto DevOps
#45Does Gitlab have equivalent for Github Team account (5 users)?
Re: What’s Next for Gitlab CI: Auto DevOps
#46I would imagine that git dominates self-hosted git. I just have bare repos on servers I can ssh into. End of problem.
Of the 2 employers I've had who self-hosted, they both did this. I've also done this when self hosting, it's super easy. I guess there are probably no surveys of this though...
It's super easy for you. I tried to set this up but it's such a pain in the backside to tell people how to pull the latest code. Ended up with Gitlab and haven't looked back.
I didn't even realise Gitlab doesn't have auto-deploy yet.. We set up a .gitlab-ci.yml script that deploys the code.
Re: What’s Next for Gitlab CI: Auto DevOps
#47"Gitlab dominates" 5% of the hosted market vs 95% of the SaaS market. And their reported popularity is based on data from a single CI company. This is further skewed since it's one of a few CI tools that actually supports Gitlab as an OAuth provider.
There's no way this claim would stand up to any scrutiny or more data-gathering. It's just marketing fluff.
EDIT: More on what upset me about this claim.
First, we have no idea of what the composition of the 10,000 applications Bitrise surveyed are like. There could be a single company that uses Gitlab to test thousands of applications that completely invalidate this result.
Second, this insults my (and every other competent readers') intelligence. This is badly done marketing. And their audience is developers. So they know they're misleading us but I guess they don't care.
Re: What’s Next for Gitlab CI: Auto DevOps
#48I would imagine that git dominates self-hosted git. I just have bare repos on servers I can ssh into. End of problem.
[deleted]
Re: What’s Next for Gitlab CI: Auto DevOps
#49Earlier quoted context omitted.
I work with self-hosted Gitlab daily and I’ve never thought the UI was bad or slow. In fact, I think it works pretty well. To the other commenters: Do you have any examples? Also, I’m excited about auto deployment. The less tools one needs to get software shipped, the better.
I've used Gitlab for personal projects on a small homelab server. I ran the VM with about 1GB of Memory and 1 vCPU (a Core i3 if I recall correctly). Loading a page could load almost instantly but most of the time it did load after 2 or 3 seconds. Gitlab does not work well when resources are scarce, it does require a bit of a beefy server to get fast and reactive, atleast in my experience. I've found Gitea/Gogs to be…
Part of this is due to Gitlab's being a Rails app. Large Rails applications are many things, but resource efficient isn't one of them. It's just the nature of the language.
Re: What’s Next for Gitlab CI: Auto DevOps
#50"Gitlab dominates" 5% of the hosted market vs 95% of the SaaS market. And their reported popularity is based on data from a single CI company. This is further skewed since it's one of a few CI tools that actually supports Gitlab as an OAuth provider. There's no way this claim would stand up to any scrutiny or more data-gathering. It's just marketing fluff. EDIT: More on what upset me about this claim. First, we have…
Stats don't make much sense. Self hosted bitbucket is huge.
I've worked for Atlassian companies lately but none of their crap calls out to the Internet and tells the mothership what they're up to. Well I guess they do. But not in a way that other people can tell. Totally not an Atlassian shill (often I wish we had gitlab) but their stuff works self hosted real well.
There's no way a third party could know what the numbers are, because when you use software which doesn't sell you out, well, you're not sold out.