Learn the kinds of constraints you should consider when evolving the software architecture of your systems in order to enable rapid, frequent release. Much of the conversation about Continuous Delivery focuses on the design of build pipelines, or the nuts and bolts of CI and infrastructure automation.

GitHub’s Matthew McCullough give an advanced tour of the Git source code management tool.

With over 2 million and a half repositories, GitHub is the world’s largest source code host. Since day one, we’ve faced an unique engineering problem: making terabytes of Git data always available, either directly or through our website. This talk offers a hopefully insightful view into the internals of Git, the way its original design affects our scalable architecture, and the many things we’ve learnt while solving this fascinating problem.

Git is a free, distributed version control system designed to handle everything from small to very large projects with speed and efficiency, which makes it perfect for indie developers. While Git has been around for a while, the tools and workflows are only now maturing. Now is the time to examine how you can benefit from using it.

Agile teams deliver their solutions in frequent small releases. This is one of the principles that is part of the Agile Manifesto: “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”

Mylyn is the task and application lifecycle management (ALM) framework for Eclipse. This talk will showcase Mylyn and the broad ecosystem which encompasses over 50 different integrations for ALM systems. We will demonstrate how tasks, source code and builds can be managed effectively with Mylyn, and examine how re-aligning collaboration around a unified notion of tasks not only accelerates developer’s adoption of Agile project management tools, but also yields a measurable productivity benefit when deployed in teams.

Do you have control over your most valuable process, the process of putting all your work into the hands of real users? If not, you’re not alone. The typical deploy in our industry is hard. Releases are few and changes are many. It’s an uncontrolled, hazardous event that is typically followed by overtime, bugs, mistakes, reckless tuning, bug fixing, and lots of praying.

As more teams move to agile development and CI to reduce delivery cycles, new requirements have emerged to ensure software quality. Manfred Moser will discuss emerging trends, best practices for ensuring quality in agile, component-based development, and new tools and techniques that development teams can leverage at build time in Jenkins.

AppHarbor deploys new versions of our users applications thousands of times every day. AppHarbor also deploys new versions of itself, usually several times a day. In this talk we will cover how we tell AppHarbor uses to structure their apps and how we have designed AppHarbor itself to be consistently and safely updated. Topics include reliable data and schema migrations, how to integrate unit tests into the delivery workflow and how to use dependency injection to build code that can be reliable developed and tested in a variety of environments.

With 1,600 jobs and 2,000 builds per day, Jenkins is a cornerstone of the Netflix build and deployment infrastructure. This talk will describe our Jenkins setup and explore some of the solutions we’ve created – and are giving back to the community – for running Jenkins at scale, including custom plugins, housekeeping jobs and configuration tips and tricks.