Go + Maven + Chef - a webinar

https://github.com/ThoughtWorksInc/go-book-config

https://github.com/ThoughtWorksInc/go-book-website
https://github.com/ThoughtWorksInc/go-book-inventory
https://github.com/ThoughtWorksInc/go-book-management

Notes:
https://dl.dropboxusercontent.com/u/6691653/webinars/go-maven-chef-notes.pdf

Update: 14th June 2013
Here's how the demo pipelines look (minus the logos) with the new value stream visualization

Update: 29th March 2013
Recording now available at the studios website.

Maven based build pipelines are fairly common. Chef based deployment pipelines are also gaining traction. In this demo, I will demonstrate how to design and connect the two using Go. Along the way I'll explain why not to use maven-snaphosts, how to make Chef talk to Nexus and provide several tips on Go usage. The resulting end-to-end automated build and deployment pipeline will provide overarching visibility, traceability, orchestration and access control for the entire continuous delivery value stream.

Date: 21st March 2013
Time: UK 10:00 AM | IN 3:30 PM | AUS 9:00 PM

Why continuous delivery needs devops, and why devops needs infrastructure-as-code

Update 02-Apr-13
Just came across this detailed relevant talk by Reinertsen - the author I reference for silo reduction and batch size reduction.


http://www.infoq.com/presentations/lean-product-dev
 
Update 31-Oct-12

Update 26-Oct-12

Slides, with notes
=====================

I'll present on this topic on 25th October 2012 as part of a ThoughtWorks Studios webinar series on continuous delivery. Please register from the webinar page.

Abstract
Continuous delivery and devops have gone mainstream, at least in terms of mindshare. As a result, a lot of vendors have jumped onto the bandwagon. Most products that have anything to do with deployment now try to associate themselves with devops and continuous delivery. In this webinar, Sriram will try to clear the air in a product independent manner. He will also cover common devops anti-patterns and explain the idea of infrastructure as code.