5 ms·
We're trending close to 1 incident every 72 hours with GitHub at work now, absolutely nuts. Lots of talk about moving stuff on-prem.
by intunderflow 4y ago
We're trending close to 1 incident every 72 hours with GitHub at work now, absolutely nuts.
Lots of talk about moving stuff on-prem.
- trinovantes 4y agoSounds like it's a bad time to be on-call at ~~GitHub~~ Microsoft
- sofixa 4y ago> Lots of talk about moving stuff on-prem. That can be complicated in itself, but GitLab's operational overhead is minimal ( both their omnibus and Helm deployment methods are highly automated) and IMHO it would be hard to have availability lower than Github's is at the moment ( last few months).
- ramraj07 4y agoWe run our CI Cd on GitHub and all our code is there and I’ve never felt there outages really affect things much ever (except the one time actions was down proper for a few hours). If anything it’s more stable than our ragged old Jenkins crap, or our airflow clusters. I’ll happily trade them to GitHub if they can take care of it. Of course we did make sure we can still deploy our code if GitHub was down but that sounds like a good redundancy practice anyway so why not?