I'm interested in seeing how tight security requirements fit in with this almost continuous deployment strategy.
Deploying at GitHub
11–20 of 61 posts
Re: Deploying at GitHub
#12Encouraging 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.
(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
#13I 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
#14Re: Deploying at GitHub
#15How 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.
[1]: http://www.etsy.com, the world's marketplace for handmade and vintage goods.
Re: Deploying at GitHub
#16Roll 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
#17I 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
#18How 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 also have regular audits with external security firms.