News for hackers. Stuff that matters.
Re:Continuous Deployment by rm-rf on Saturday February 12, 2011 @12:05PM (#2210434)
I've seen single line changes cause data loss, corruption, system outages, remote root exploits...

I'm not sure that the number of lines makes the change more or less risky.

Re:Continuous Deployment by ichverstehe on Saturday February 12, 2011 @12:16PM (#2210471)
And how exactly does this relate to the way they deploy their code? As far as I can tell, they actually review code before marking it ready for deploy. That kind of changes would be an issue with "usual" large batch deploys as well.
Re:Continuous Deployment by chaz on Saturday February 12, 2011 @12:57PM (#2210573)
I've also seen many devs look at a broken release and instantly realize their mistake. A forgotten production config, a hard coded variable, or an empty cache. If code is in fact reviewed before going to production, the risk is significantly lower.
Re:Continuous Deployment by cool-RR on Saturday February 12, 2011 @01:06PM (#2210602)
Nice choice of username, by the way.
Re:Continuous Deployment by MartinCron on Saturday February 12, 2011 @10:44PM (#2211965)
The safest change to make to a stable system is the smallest change possible.