EDIT: (21:00 UTC ) Just got in :D
GitHub Is Down
41–50 of 93 posts
Re: GitHub Is Down
#42That's great. 2 minutes before it went down a pipeline workflow ran in Heroku deploying a bug to my app. Now I can't deploy the hotfix since it depends on Github and I'm not able to revert to the last successful build on the Heroku interface. Any ideas?
Remove spiderweb dependencies from your deployment pipeline?
One of the things a site reliability engineer should think about is how well the site can be operated when dependencies have issue. After an incident like this, even if you were able to recover, it's worth thinking about how things could have gone better.
In the past I had a painful experience with one application I was supporting that needed to install NPM packages on deployment. We couldn't successfully deploy (or scale up) for the duration of that outage. In that case we realized it was safer to switch to server images with all assets pre-installed and an NPM cache to give the build a better chance of succeeding. The next NPM outage we only noticed after the fact :)
Not certain how this particular deployment pipeline is failing due to the GitHub outage, but a post-mortem to discuss may be helpful and protect against future issues.
Re: GitHub Is Down
#43Re: GitHub Is Down
#44Re: GitHub Is Down
#45https://twitter.com/PonteIneptique/status/783190337602846720
Re: GitHub Is Down
#46Phishing email looks like a "review your suspicious activity" alert, but the alert is the suspicious activity.
Re: GitHub Is Down
#47Amazing!
Re: GitHub Is Down
#48Re: GitHub Is Down
#49Even our static assets from raw.githubusercontent.com are throwing 500s. Whatever it is, it sounds like a pretty widespread failure...
Re: GitHub Is Down
#50We use a self-hosted GitLab ourselves and I can honestly say we have more up time than GitHub. But 9/10 every project we use is on GitHub and our work is stalled. Centralization will be our downfall :(
https://docs.gitlab.com/ee/user/project/repository/repositor...
Congrats on the self-hosted uptime :)