GitHub - Major Service Outage(status.github.com) |
GitHub - Major Service Outage(status.github.com) |
https://code.google.com/p/gittorrent/
For a variety of reasons.
...oh.
wouldn't your critical shit break long before you go read about it on HN? otherwise, why not just rely on their human-friendly status pages that get served if such a thing occurs?
i don't understand why this is on the front page, since it's not an infrequent occurrence.
but many (all?) submissions that make it to the front page get there by being manually curated there, not by accumulating upvotes first. on the flip side of the same coin, a lot of good things never make it to the front page, even if they gain a lot of points.
I'd suggest a rule of thumb where a build ought to be able to complete without any resources that you don't control the uptime of. As the number of such resources increases, the amount of time the build can not actually be built will tend towards 100%. A git caching proxy would be great for that sort of thing. A generic DVCS proxy would be even better.
ooops?
I'm not trying to blame Github though, they're awesome!
On a previous team we developed the mental image of a bicycle, consisting of two cycles.
It seemed to help at the time.. but now I think about it I'm not sure how it did!