Continuous Delivery

the nuts and boltsBRINGING IT TO WOOLWORTHS

The Past…

Deployments - last minute - others

got to play TT

Folders

Databases including rollback scripts

Web.Config!

Release notes

Pain for everyone

Deployment time measured in hours

and repeated for each

environment

Present aka the pipeline

Deployments - automated

Folders use MSBuild

Transforms use msbuild

Database use Fluent Migrations

Release Notes use PowerShell script with

team city API

Deployment time from build to TEST

environment WW ~10 minutes

Implementation of pipeline

Came out of retrospective which

highlighted issues with current

deployment processes

Got 1 week sprint in mid Feb

Completed MS build scripts

Integrated FluentMigrator

Created packages to be consumed by Octopus Deploy

FTW

Allowed us to fail fast

Release to production cadence increased

Moved away from big mono lithic releases

Reuben’s Buckets

A build bucket

Stuff for the build aka state

A release bucket

Environment

Build components

TFS build was complex

Can test MSBuild scripts locally

Code reuse

Release Notes

Tests, CI, Catch migrations issues

Release

All the cool kids were using it

Great visibility of version in specific environment

Great for providing structure to automate releases

Has API to further

Code reuse

.Net focused

Transforms now live here

Is more suited for release where you own the metal

Patai [Questions]