Continuous Delivery in a .NET World

Continuous Delivery in a .NET World

Adam GoucherTuesday, November 11, 14

Have A Goal

Tuesday, November 11, 14

Have A GoalYou cannot win if you don’t know what winning looks like.


Get ‘trunk’ deliverable


Get ‘trunk’ deliverableFeature Flags


Get ‘trunk’ deliverableExternalized Configuration


Get ‘trunk’ deliverableNon assumption of installation location


Get ‘trunk’ deliverableStop branching!!!


Figure out your database


Figure out your databaseInfluences your tooling


Figure out your databaseInfluences your build chain


Figure out your databaseForwards and backwards change compatibility within the

application


Figure out your databaseInfluences deployment process


Convention over Configuration


Convention over ConfigurationSolution / Projects should be clones of each other


Convention over ConfigurationIt doesn’t matter if your ‘partners’ don’t like it


Make things Small (And Modular)


Make things Small (And Modular)Nuget to the rescue?


Not All Chains are Equal


Not All Chains are EqualBe rigid. Except when you are flexible.


Automate what should be Automated



Continuous Deployment vs. Continuous Delivery



Natively


Infrastructure Matters


Infrastructure MattersIf you have a ‘DevOps team’...


Infrastructure MattersThe first hit is free...


Infrastructure MattersInfrastructure is a ‘Product’ as well


Powershell


PowershellWhen you need a Hammer


Its all about the People


Its all about the PeopleDuh!


Its all about the PeoplePeople, not Resources


Its all about the People/Everyone/ needs to believe


Its all about the PeopleGet rid of those that don’t


It isn’t easy...


...but is now possible.


Start NOW!


Technology