Daniel Worthington-Bodart presents ways to reduce the built times by a factor of 10.
Jinesh Varia discusses automating continuous integration, continuous deployment and continuous optimization in the context of using cloud computing services.
Ryan Slobojan discusses how to perform issue tracking, code review, commits and builds in an automated manner by integrating Git, Gerrit, Hudson and Mylyn.
Godfrey Nolan discusses using CI for iOS and Android apps, headless emulators, tools for unit and functional testing, and mobile app deployment.
Carl Quinn presents the build and deployment architecture used by Neflix in order to provide content out of Amazon AWS.
Jez Humble discusses innovating using a Lean startup approach and overcoming innovation barriers in enterprises along with engineering practices useful for rapid delivery of quality software.
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.
Chris Read describes a situation where they had to gradually reorganize a development process standardizing the build and deployment scripts, adding CI, automating everything, staging the binaries.
Kohsuke Kawaguchi discusses the future of Continuous Integration and Jenkins as they will be influenced by virtualization, cloud computing, DVCS and analysis software.
Jez Humble talks on the importance of Continuous Delivery for a business, outlining the foundational principles and practices to be implemented for a successful CD, explaining how to do continuous integration, various ways of testing, canary releasing, and migrating data.
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.
Rolf Russell & Andy Duncan discuss how to have rapid and reliable releases from the perspective of build, release, and devops, considering the relationship between the teams involved, the metrics needed to measure the performance achieved, the required skills, and the need to remove waste and bottlenecks.