6 ms·
I wish GitLab would take whatever resources this has and put them all on site reliability. They have a ton of open positions listed, but none are for Site Reli
by snurk 8y ago
I wish GitLab would take whatever resources this has and put them all on site reliability.
They have a ton of open positions listed, but none are for Site Reliability Engineer.
Frequent slow requests and 5xx errors keep me from giving GitLab a real try.
- sytse 8y agoGetting GitLab.com reliable is a top priority. We are hiring multiple SREs and https://jobs.lever.co/gitlab/a9ec2996-b7b6-4d87-aed0-1fc2ce3f8faa https://jobs.lever.co/gitlab/a9ec2996-b7b6-4d87-aed0-1fc2ce3... is on our jobs page.
- erikb 8y agoYou can't have a gazillion features and be stable. I think it's quite clear which direction Gitlab is going.
- golergka 8y agoAnd performance. I migrated our project from Gitlab to Githab exactly because of how excruciatingly slow PR workflow was (serialized game assets routinely have changesets in tens of thousands of lines).
- philipwhiuk 8y agoGit-fat/GFS and treating assets as binary would seem to be the solution here. There's no way you can review tens of thousands of lines.
- golergka 8y agoWhen they're in tens of thousands, no. But quite often files of the same format, and even the same files have just a couple of changes that are definitely reviewable.