David Norton

Continuous delivery is the very first principle behind the Agile Manifesto, and yet it continues to plague software development teams. In this talk, David Norton will give a brief overview of continuous delivery practices and then focus on the area that engineers have the most control over: the build phase. Learn about continuous delivery in the light of source control, dependency management, and automated testing strategies. Go back to work with the confidence that you will be able to improve delivery practices on your own team! Gradle will be used in the examples but the principles will work for Maven and other tools as well.

Original code and slides.

Share this Post

Related Blog Posts

JVM

Using Groovy Based Spring Configuration

January 12th, 2016

A guide to using Groovy for Spring configuration both JavaConfig and Grails style and adding Groovy configuration to web.xml using ContextLoaderListener.

Object Partners
JVM

Changing the embedded server in Grails 3

January 7th, 2016

How to change the server from Tomcat to something else in Grails 3s fat jar

Mike Hostetler
JVM

Flirting with disaster: A dangerous use of Groovys dynamic method invocation

January 5th, 2016

An example of when not to use Groovys dynamic method invocation feature. Injection attack vulnerability.

Object Partners

About the author

David Norton

Principal Consultant

Software engineer with 9 years of professional application development experience. Passionate about continuous delivery, incremental improvement, and test-driven development.

Background heavy in enterprise Java technologies such as Groovy, Spring, Spock, Gradle, Hibernate, Tomcat, Jenkins. Focus on high-scale web architecture, platform transformation, and team development.