Previously, I covered, at a high level, how our builds work [https://blog.dadops.co/2013/10/12/how-we-deliver-features-to-pinners/] and what tools we used [https://blog.dadops.co/2013/10/06/tools-we-use-to-release-pinterest/]. I wanted to explain what exactly we are doing during a deploy, with an emphasis on tracking state.
Previously we discussed what tools Pinterest uses for deploys [https://blog.dadops.co/2013/10/06/tools-we-use-to-release-pinterest/]. This article shows how we connect them to create a “pipeline.” In practice, Pinterest is a continuous delivery shop. That means at any given time we can serve the latest code our engineers
We have a fairly flexible Continuous Delivery system at Pinterest. The tools we use are fairly accessible, so you can build your own Continuous Delivery system too. * Github Enterprise [http://enterprise.github.com/] is our version-control overlay. It manages code-reviews, facilitates code-merging, and most importantly has a great API. The