Många agila organisationer inför continuous delivery som ett steg mot att snabbare leverera affärsnytta från IT projekten. Men hur får man det att fungera på riktigt? I denna session går vi igenom hur vi inför tekniker och verktyg för att bygga, paketera, driftsätta och testa en komplex applikation i god agil DevOps anda. Vi kommer använda Azure och Visual Studio Team Services för att bygga en leveransprocess med den senaste tekniken. I sessionen går vi självklart igenom de viktigase beståndsdelarna i en continuous delivery process. Vi kommer dessutom ta dina färdigheter till nästa nivå genom att titta på koncept som feature driven development, infrastructure as code, versionshanterad konfiguration och canary deployments.

1. Continuous Delivery
Mathias Olausson
CTO, Solidify AB
Mathias.Olausson@Solidify.se

3. Tom Goodwin

5. “Continuous Delivery is a software development discipline where
you build software in such a way that the software can be released
to production at any time”

6. How does CD help?

7. How does CD help?
1. Helps you build the right thing
Release small chunks
of functionality
frequently.
Get regular customer
validation of the
product’s value
Incorporate feedback
rapidly. Fail fast and
learn fast.
Release
Get
Feedback
Improve

8. How does CD help?
1. Helps you build the right thing
2. Reduces risk of releases
1 1
2
1
2
3
1
2
3
4
1
2
3
4
5
2
3
4
5
1
6
2
3
4
5
1
6
7
Time
Unreleased
1
1
2
1
3
2
1
4
3
2
1 2
3
4
5
1
3
4
5
6
2
1
3 4 5 6 72 Unreleased
Released
VS

9. How does CD help?
1. Helps you build the right thing
2. Reduces risk of releases
3. Delivers real progress
RELEASE CHECKLIST:
 Regression Testing
 Integration Testing
 User Acceptance Testing
 Infrastructure Setup
 Performance Testing
 Security Audit…
“Done” is no longer “dev-
complete”, but is thoroughly
validated as only a release can.

10. Source Control Continuous
Deployment
Code Editing Unit Testing Code AnalysisDebugging Continuous
Integration
<//>
public async Task<int>
{int x = await task;
Continuous Delivery

11. Stage 1: Building Software

12. Team Collaboration

13. Branching Strategies

14. Semantic Versioning
1.2.3-beta1
version risk
build increment (patch)
http://semver.org/

15. Feature Toggles

16. Feature Toggles

17. Build Automation

18. Stage 2: Optimizing

19. Release Pipeline

20. Infrastructure as Code

21. Quality Assurance
Exploratory testing
Unit tests
Functional tests
UI tests
Performance tests
Security tests
…

22. Stage 3: Rethinking

23. Deployment Pattern #1
Linear deployment
DEV
QA
PRODUCTION

24. Deployment Pattern #2
Fan-out, ad-hoc deployment
DEV
UAT PRODUCTIONCapacity
Automated
Tests

25. Deployment Pattern #3
Fan-out, fan-in deployment
DEV
QA
PRODUCTION
Capacity Automated Tests

26. Deployment Pattern #4
Canary/Staged deployment
Ring2
Ring 1
Ring 0

27. Deployment Pattern #5
Blue-Green deployment

28. Measure and Learn

29. Application Insights
Exceptions and performance diagnostics
Availability monitoring
Data analysis
Proactive detection

30. Release Annotations
Create annotation from release on
the AI metrics timeline
Available as an extension from the
Visual Studio Marketplace

31. Rethink the way we deploy
Continuous Delivery
Build
App
Deploy to
Test
Test
Deploy to
QA
Test
Deploy to
Prod
Continuous Delivery with Containers
Build
Container
Deploy
Container
to Test
Test
Deploy to
QA
Test
Deploy
Container
to Prod
Build
App

32. Deliver, Learn, Improve

33. Don’t miss this:

34. meetup.com/swedish-ms-alm-devops/

35. Thank you!
Mathias Olausson
mathias.olausson@solidify.se
@molausson