a pragmatic approach to continuous delivery

A Pragmatic Approach to Continuous DeliveryIvar Grimstad

jDays 2012 Ivar Grimstad1

2012-12-03 e.g. name of the presenter2

@ivar_grimstad


• JUnit

• Ant

• Continuous Integration

• Maven

• Continuous Delivery

A Little History


Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Agile Manifesto


http://www.agilemanifesto.org/

Our highest priority is to satisfy the customer

through early and continuous delivery

of valuable software.

Welcome changing requirements, even late in

development. Agile processes harness change for

the customer's competitive advantage.

Deliver working software frequently, from a

couple of weeks to a couple of months, with a

preference to the shorter timescale.

Business people and developers must work

together daily throughout the project.

Build projects around motivated individuals.

Give them the environment and support they need,

and trust them to get the job done.

The most efficient and effective method of

conveying information to and within a development

team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development.

The sponsors, developers, and users should be able

to maintain a constant pace indefinitely.

Continuous attention to technical excellence

and good design enhances agility.

Simplicity--the art of maximizing the amount

of work not done--is essential.

The best architectures, requirements, and designs

emerge from self-organizing teams.

At regular intervals, the team reflects on how

to become more effective, then tunes and adjusts

its behavior accordingly.

Principles behind the Agile Manifesto



Our highest priority is to satisfy the customer

through early and continuous delivery of valuable

software.

Principles behind the Agile Manifesto



Welcome changing requirements, even late in

development. Agile processes harness change for

the customer's competitive advantage.

Deliver working software frequently, from a

couple of weeks to a couple of months, with a

preference to the shorter timescale.

Business people and developers must work

together daily throughout the project.

Build projects around motivated individuals.

Give them the environment and support they need,

and trust them to get the job done.

The most efficient and effective method of

conveying information to and within a development

team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development.

The sponsors, developers, and users should be able

to maintain a constant pace indefinitely.

Continuous attention to technical excellence

and good design enhances agility.

Simplicity--the art of maximizing the amount

A Pragmatic Approach to Continuous Delivery

Motivation


• Build Binaries Once

• One Process Deploy

• Test Deployments

• Flow

• Fail -> Stop the Line

The Deployment Pipeline


• Commit

• Analysis

• Deploy

• Test

• Deliver

Remember that this is a pragmatic approach

Deployment Pipeline Stages


• Compile

• Test

• Create binaries for later use

The Commit Stage - Steps


The Commit Stage - Example


• Static Analysis

The Analysis Stage - Steps


• Test Coverage

• Duplications

• Complexity

• Coupling

• Rule Compliance

• Code Style

The Analysis Stage - Metrics


Sonar


The Analysis Stage - Example


• Copy Artifact from Commit Stage

• Deploy to Test Environment

The Deploy Stage - Steps


The Deploy Stage - Example


• Choose a subset of tests to run

• Run tests most likely to fail first

The Test Stage - Steps


The Test Stage - Example


• Copy Artifact from Commit Stage

• Deliver according to agreement

The Deliver Stage - Steps


The Deliver Stage - Example


Jenkins Build Pipeline Plugin


• Use Maven Release Plugin

– mvn release:branch or mvn release:prepare

– mvn release:perform

• Jenkins Fingerprint Functionality

What about Versioning?


Do not underestimate JavaDoc!

What about Documentation?


• Blue/Green Deployments

• Canary Releasing

• Feature Toggles

• Branch by Abstraction

Designing for Continuous Delivery


• Manual Deployment

• Deployment to production-like environment after

development is complete

• Manual configuration of production environment

• Excessive Branching

Antipatterns


• Every change should trigger the feedback process

• Fast Feedback

• Act on the Feedback

To Sum Up


• Jenkins

– Build Pipeline Plugin

– Copy Artifact Plugin

• Sonar

• Maven

– Maven Release Plugin

– Maven Javadoc Plugin

– Maven Glassfish Plugin (similar for all app servers)

Tools


• Define your pipeline steps

• Set up the jobs

• Start configuring

• Evolve your pipeline

Where to start?


• Architecting for Continuous Delivery

Axel Fontaine

Tuesday 14:40

• Building a Continuous Deployment Pipeline with Maven

Alan Parkinson

Wednesday 13:30

More at jDays


It is not that hard!

Remember…


You’re probably doing it already!

…and


@ivar_grimstad

http://www.agilejava.eu


a pragmatic approach to continuous delivery

Technology