4 ms·
I wish Gitlab would just fix up their existing product instead of increasing the surface area. Every month they put out a security release that often contains a
by jenny91 4y ago
I wish Gitlab would just fix up their existing product instead of increasing the surface area. Every month they put out a security release that often contains a couple of "high severity" bugs and every couple of months there's a "critical" one. And they're not rocket science either, simple auth check bypasses and so on. Clearly something's not going right in the culture if you have multiple critical security bugs every year.
I am increasingly antsy about hosting my private Gitlab instance on the web, and this does not reduce that.
- zachruss92 4y agoI got burned so many times by GitLab I can't in good conscience use them anymore. I always try to use an OSS product when I can, but I literally lost a client a few years back because we couldn't do a deploy because GL was down. For now I use GH for critical projects and a self hosted Gitea instance when it's not super critical.
- choward 4y agoOne of the benefits of gitlab is you can host it yourself. Github has also had outages.
- AlexErrant 4y agoTo be fair, Github actions has a spotty record as well. https://www.githubstatus.com/history https://www.githubstatus.com/history
- tapoxi 4y agoOn the flip side, we switched to our own hosted-on-k8s GitLab summer 2019 and it's been rock solid since. I patch it monthly (via Helm) and it's painless. About 100 users and it handles all of our CI, which runs on a separate GKE node pool.
- mekster 4y agoIt does feel like GitLab is at do everything and do it at 70% efficiency of dedicated tools, zone and with the trend of being slow and constant bugs, the internal must be too complicated for developers to grasp and that kind of project can never get out of that trend unless rewritten efficiently. Gitea is a good example of, do less stuff and do those well zone.