3 ms·
Honestly sounds like an implementation issue. I've run multiple Gitlab instances and I've used some more, and "crashes all the time" isn't a thing that just hap
by sofixa 5y ago
Honestly sounds like an implementation issue. I've run multiple Gitlab instances and I've used some more, and "crashes all the time" isn't a thing that just happens. Most features work fine, core ones even more so, some of the newer ones are clearly not polished enough but mostly function.
It's literally years in front of the competition ( GitHub and BitBucket).
- secondaryacct 5y agoHow many thousands repos do you have ? We are 10k+ users with many many more repos scattered around the world. But the thing I ll say is the git part is satisfactory. It's the CI part we are livid about. It's not "years in front of the competition" if you think of Teamcity. Github focus on what it does right.
- sofixa 5y agoI'd say 5-6k users, and the number of repos is easily between there and 10k on the biggest Gitlab instance I've used. The CI/CD part works well, including for complex multi-project dynamic pipelines. We don't have crashes, ever. > It's not "years in front of the competition" if you think of Teamcity. Github focus on what it does right. The competition for me is the all-in-one solutions like Github and Bitbucket. If you have to deploy, maintain and sometimes pay for an extra CI/CD solution, either something is wrong or you have very very specific requirements. What is it that TeamCity does better than Gitlab CI/CD?
- secondaryacct 5y agoI was gonna write a long list of doleances but you know what, Ill give it a chance after all. We re still learning it, we ll figure it out I guess, and if it's cheaper, well, it s more money for shareholders.