P5h5eahxd6mpdrbbuqza
SkillsCast

Continuous Delivery Patterns for Large Software Stacks

13th March 2013 in London at Skills Matter

This SkillsCast was filmed at Continuous Delivery Patterns for Large Software Stacks

During this talk, Hans Dockter will look at common patterns for building larger software stacks and discuss their advantages and disadvantages.

This is a critical problem for many teams. Hans will share many stories of real life projects, how they were affected by a dysfunctional pipeline and what it took to improve their situation.

There are quite a few larger projects for which a naive practice of early integration between their components lead to constant breakages and a defect delivery pipeline. Thus they were not capable to successfully build a new version of the software stack for days or even weeks.

Obviously the problem of that is dramatic as no regular manual testing and capacity testing is taking place. Not only is this a massive waste of testing resources, it also leads to very long and therefore expensive feedback cycles that severely affect your time-to-market of new features.

It also a likely source of conflict between the CI team and software development, as with no other means at hand, there is a desire to create stability by not adding new features or doing important refactorings.

YOU MAY ALSO LIKE:

Continuous Delivery Patterns for Large Software Stacks

Hans Dockter

Hans Dockter is the founder and project lead of the Gradle build system and the CEO of Gradleware Inc, a company that provides training, support and consulting for Gradle and all forms of enterprise software project automation in general.

SkillsCast

During this talk, Hans Dockter will look at common patterns for building larger software stacks and discuss their advantages and disadvantages.

This is a critical problem for many teams. Hans will share many stories of real life projects, how they were affected by a dysfunctional pipeline and what it took to improve their situation.

There are quite a few larger projects for which a naive practice of early integration between their components lead to constant breakages and a defect delivery pipeline. Thus they were not capable to successfully build a new version of the software stack for days or even weeks.

Obviously the problem of that is dramatic as no regular manual testing and capacity testing is taking place. Not only is this a massive waste of testing resources, it also leads to very long and therefore expensive feedback cycles that severely affect your time-to-market of new features.

It also a likely source of conflict between the CI team and software development, as with no other means at hand, there is a desire to create stability by not adding new features or doing important refactorings.

YOU MAY ALSO LIKE:

About the Speaker

Continuous Delivery Patterns for Large Software Stacks

Hans Dockter

Hans Dockter is the founder and project lead of the Gradle build system and the CEO of Gradleware Inc, a company that provides training, support and consulting for Gradle and all forms of enterprise software project automation in general.

Photos