Live data from Hacker News

Deploying at GitHub

github.com

11–20 of 61 posts

Re: Deploying at GitHub

#11
How often does code go through security audits? Is every feature audited prior to deploying to live? GitHub is making money by selling private repositories which will often contain very sensitive code, so ensuring nobody can gain unauthorised access to them is presumably one of the top concerns.

I'm interested in seeing how tight security requirements fit in with this almost continuous deployment strategy.

Re: Deploying at GitHub

#12
post #6

Encouraging to know this model scales to 100 employees at least. Purely out of intellectual interest, I wonder if a company the size of Google or Facebook could also ship in this way, or if the whole release manager/team is essential.

Sarbanes-Oxley puts a big damper on production deployments at big companies. I don't fully understand it so I won't try to explain it.

(I will complain though: the law says developers shouldn't have control over production systems. If that's a requirement, who's going to write the software?)

Re: Deploying at GitHub

#13
How do you deal with the github enterprise version of your software? Does it have a separate QA cycle? How often do you ship new releases of that?

I am hoping that Github could shed more light on the how they ship an enterprise version along with the SAASy web version that we all know and love.

Re: Deploying at GitHub

#15

How often does code go through security audits? Is every feature audited prior to deploying to live? GitHub is making money by selling private repositories which will often contain very sensitive code, so ensuring nobody can gain unauthorised access to them is presumably one of the top concerns. I'm interested in seeing how tight security requirements fit in with this almost continuous deployment strategy.

We do continuous deployment at Etsy[1] as well. Here is a talk from our head of application security (probably not his official title, fyi) about some of the stuff we do: http://www.slideshare.net/zanelackey/effective-approaches-to....

[1]: http://www.etsy.com, the world's marketplace for handmade and vintage goods.

Re: Deploying at GitHub

#16
I might be wrong but for me this is almost a [Hack] -> [Prod] methodology...

Roll back in 30 seconds, cool but how do you manage data / schema migrations ? You have a snapshot also to rollback any data corruption the last hacking session could have introduced ?

Re: Deploying at GitHub

#17
post #16

I might be wrong but for me this is almost a [Hack] -> [Prod] methodology... Roll back in 30 seconds, cool but how do you manage data / schema migrations ? You have a snapshot also to rollback any data corruption the last hacking session could have introduced ?

Data migrations are done carefully with the Large Hadron Migrator Ruby gem: https://github.com/soundcloud/large-hadron-migrator. Facebook has a similar tool: https://www.facebook.com/note.php?note_id=430801045932

Re: Deploying at GitHub

#18

How often does code go through security audits? Is every feature audited prior to deploying to live? GitHub is making money by selling private repositories which will often contain very sensitive code, so ensuring nobody can gain unauthorised access to them is presumably one of the top concerns. I'm interested in seeing how tight security requirements fit in with this almost continuous deployment strategy.

Every commit is reviewed by at least 1 person. Depending on the feature, several people may chime in. I find that reviewing smaller diffs is much easier. We also use Team Mentions (@github/api, for example) liberally to get more eyeballs.

We also have regular audits with external security firms.

Post reply on HN