Hans Dockter discusses build systems from a declarative vs. imperative perspective, the importance of a rich execution model and problems with POM, providing examples from Gradle, Maven and Ant.
Rachel Laycock discusses using a polyglot build and deployment infrastructure that makes life easier.
John Penix describes the test automation system and the supporting build system infrastructure used by Google.
Peter Walker discusses and demoes some of Gradle’s features: declarative build, convention over configuration, plugins, multi–project support, partial builds and increments, Ant and Maven integration.
John Stevenson introduces Leiningen 2, a build system for Clojure, explaining how to set it up and how to use it.
Paul Grenyer discusses why and how to create a Walking Skeleton - an implementation of the thinnest possible slice of real functionality that we can automatically build, deploy and test end-to-end.
Baruch Sadogursky demonstrates automated building techniques using Maven/Gradle/Custom scripts and Binary Repository along with common pitfalls that are to be avoided.
Daniel Worthington-Bodart presents ways to reduce the built times by a factor of 10.
Carl Quinn presents the build and deployment architecture used by Neflix in order to provide content out of Amazon AWS.
Ryan Slobojan presents Code2Cloud used to automatically set up a number of tools useful for development and deployment: Hudson, Git, task repository, wiki, Cloud Foundry Deployment Services and Maven.
Kohsuke Kawaguchi discusses the future of Continuous Integration and Jenkins as they will be influenced by virtualization, cloud computing, DVCS and analysis software.
Ashish Kumar presents how Google manages to keep the source code of all its projects, over 2000, in a single code trunk containing hundreds of millions of code lines, with more than 5,000 developers accessing the same repository.