4 ms·
We use gitlab.com for code reviews and CI, and we basically lost a day of integration productivity because of it. Yes, our process is too tightly tied to a sin
by beefsack 10y ago
We use gitlab.com for code reviews and CI, and we basically lost a day of integration productivity because of it.
Yes, our process is too tightly tied to a single service, but it happens because we don't have the resources to self-host our own solution. We love GitLab, but this has absolutely got us looking elsewhere.
- balls187 10y agoHow many days of productivity are you going to lose migrating off GitLab ?
- Gracana 10y agoAnd how do you ensure you're not going to have the same problem at the next place.
- diegoperini 10y agoAnd what will you do if the next place people doesn't tell you the root cause of a probable similar event?
- jonknee 10y ago> We love GitLab, but this has absolutely got us looking elsewhere. If you love GitLab and don't want to self host you can pay them for GitLab Hosted (paid customers had no troubles today).
- mdekkers 10y agoThe gitlab service is obviously important to your organisation, but not important enough to pay for their service, and incidentally, support a more robust environment?
- pricechild 10y agoDo you self-host any services currently & have they incurred any similar unexpected downtime in the past? If you self-hosted code reviews/CI, would you expect having a similar downtime causing problem in the future? I expect the answer to be "Yes" for most companies.