<story><title>Continuous Deployment at Instagram</title><url>http://engineering.instagram.com/posts/1125308487520335/continuous-deployment-at-instagram/</url></story><parent_chain></parent_chain><comment><author>madetech</author><text>Shameless Plug: I&amp;#x27;ve recently been involved in writing a book on Continuous Deployment, which covers many of the points Instagram are writing about here (but in greater detail).&lt;p&gt;I&amp;#x27;ve got ~1,000 printed copies to give away. So if anyone wants one, go here: &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;madete.ch&amp;#x2F;1S3OGvl&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;madete.ch&amp;#x2F;1S3OGvl&lt;/a&gt; and follow the link on the left hand side and we&amp;#x27;ll mail a copy to you.</text></comment>
<story><title>Continuous Deployment at Instagram</title><url>http://engineering.instagram.com/posts/1125308487520335/continuous-deployment-at-instagram/</url></story><parent_chain></parent_chain><comment><author>avolcano</author><text>Also seconding the confusion that other commenters have regarding the &amp;quot;three commits max&amp;quot; rule for automated deploys. Maybe engineers at Facebook are just big fans of rebasing, but I often make commits on feature branches that don&amp;#x27;t &amp;quot;stand on their own&amp;quot; - i.e., would break some functionality without subsequent commits. I&amp;#x27;m not sure why you&amp;#x27;d want to deploy one-commit-at-a-time unless you kept a very strict &amp;quot;one commit == one standalone feature&amp;#x2F;bugfix&amp;quot; rule, which isn&amp;#x27;t mentioned in this post.&lt;p&gt;(I suppose it&amp;#x27;s also possible that that&amp;#x27;s referring specifically to &lt;i&gt;merge commits&lt;/i&gt; into master, which would make a lot more sense to me)</text></comment>