17
@ Continuous Delivery 101 Matteo Emili http://blogs.ugidotnet.org/j3r http://mattvsts.blogspot.com [email protected] @MattVSTS

ALM@Work - Continuous delivery 101

Embed Size (px)

DESCRIPTION

Sessione "Continuous delivery 101" tenuta da Matteo Emili all'evento "ALM@Work" di DomusDotNet il 28/09/2012

Citation preview

Page 1: ALM@Work - Continuous delivery 101

@Continuous Delivery 101

Matteo Emilihttp://blogs.ugidotnet.org/j3rhttp://mattvsts.blogspot.com

[email protected]@MattVSTS

Page 2: ALM@Work - Continuous delivery 101

Grazie agli sponsor

Page 3: ALM@Work - Continuous delivery 101

@REQUIREMENTS

PRODUCTBACKLOG

OPSBACKLOG

MonitorImplement

WORKING SOFTWARE

DefineIdeation

DevelopIdea to working software

OperateWorking software in productionValue realization

Users/Stakeholders

Development & testing

Operations

Delivery

Page 4: ALM@Work - Continuous delivery 101

@• A methodology of automation• No more unexpected problems at

deployment time

• A quality enhancer• Early fails are the best way of

understanding systems’ complexity

• A business driver• You spent a hour fixing a bug, but the fix

won’t be out before the first patch (average waiting?)

What is it?

Solution

Page 5: ALM@Work - Continuous delivery 101

@Continuous Integration

What is it not?

Continuous Deployment

It doesn’t deploy!

Deploy is tied to a certain environment

Problem

Page 6: ALM@Work - Continuous delivery 101

@Less overall defect rate in the systemFast feedback from the customer

Incremental changes

Decreased costsDecreasedcycle times

Satisfied users & stakeholders

Page 7: ALM@Work - Continuous delivery 101

@DEMO

Continuous Delivery basicsImplementing Continuous Delivery

Page 8: ALM@Work - Continuous delivery 101

@• Web.config transformations• Custom MSBuild tasks• Custom WF activities

• They might incur in friction!

There is more to be added

Page 9: ALM@Work - Continuous delivery 101

@• Community-driven workflow activities

• Tons of contribution from Blue Badges and MVPs (Mike Fourie, Richard Fennell, Ed Blankenship)

• http://tfsbuildextensions.codeplex.com/

Link: Community TFS Build Extensions

Page 10: ALM@Work - Continuous delivery 101

@ACME Corporation is a company willing to employ the newest technologies in the market to maximize earnings

They invested in Windows Azure with satisfaction...

...they want more, with Visual Studio ALM 2012

Case study: ACME Corp

Page 11: ALM@Work - Continuous delivery 101

@• Windows Azure Web Sites• ASP .NET

• Visual Studio ALM 2012• Visual Studio 2012 Ultimate• Team Foundation Service• Team Build 2012

Technical scenario

Page 12: ALM@Work - Continuous delivery 101

@• We can link a Team Foundation Service team project to a Windows Azure website

• Automatic deploy, redeployments, etc.

Team Foundation Service + Azure

Page 13: ALM@Work - Continuous delivery 101

@DEMO

Continuous Delivery in the cloudTeam Foundation Service and Windows Azure

Page 14: ALM@Work - Continuous delivery 101

@• On premise we can get 100% flexibility, but with a higher complexity rate

• The cloud avoids this giving us some infrastructural constraints

On premise…and in the cloud

Page 15: ALM@Work - Continuous delivery 101

@• Continuous Delivery allows to create the most friction-less process for software development

• Technologies can be a great aid (VSTLM…)

No friction

Page 16: ALM@Work - Continuous delivery 101

@Questions?Doubts?

“Not useful!”“Willing to see

more!”

Roundtable

Page 17: ALM@Work - Continuous delivery 101