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, outlining principles and practices, explaining continuous integration, various ways of testing, canary releasing, and migrating data.
Ashish Kumar on how Google keeps the source code of over 2000 projects in a single code trunk containing 100s of M of code lines, with more than 5,000 developers accessing the same repository.
Rolf Russell & Andy Duncan discuss rapid and reliable releases from the build/release/devops perspective, considering relationships, metrics, required skills, and the need to cut waste and bottlenecks
Robert C. Martin on writing good code starting with a bad code example, then addressing many topics like: Boy Scout rule, functions, arguments, craftsmanship, TDD, engineering, certification, etc.
This talk outlines innovations in tools, process, planning and culture emerging at the front lines of continuous delivery.
Dan North discusses an example of rearchitecting an application without rewriting it from scratch, and explains general strategies for a holistic rearchitecture.
This session will attempt to answer all those questions and more. The presenter will share his experiences of 5 years of being a professional build manager, using examples taken from real projects.