Have you ever been unable to reach GitHub during a denial of service attack? They're supposedly rare, but I've been committing during three of them in the last

Have you ever been unable to reach GitHub during a denial of service attack? They're supposedly rare, but I've been committing during three of them in the last year. Simply, they're not dependable and if you deployment mechanism needs to be dependable then you're adding a rather weak link to the chain. Obviously you could host/mirror git locally for more robustness, but it will be yet another system you depend on. It is for this reason that every enterprise I've worked at used a solution where a tar ball of the code to be deployed was composed, archived, and then pushed out to ensure it was available for all nodes and that old versions were available for rollbacks. As a simple example of the above, my TeamCity server builds all commits, then pushes successful war files to S3, then contacts all the server nodes that fetch their deployment code from S3, which has 11 9's durability.