ContinuousDelivery-101

1. Webinar Series Continuous Delivery
in the Enterprise
Continuous Delivery 101

2. CI-CD-Agile-Automation and what not!
2

3. Agenda
• What is Continuous Delivery?
• I thought I knew CI, Agile, Quality and DevOps!
• Continuous development, integration and the ability to continuously release
– The CD Pipeline
• Key aspects and players
• What’s my role in CD and why should I care?
• Work, Gamified!
• CD Tools, Products and Solutions out there!
• Wrap-up: Case Studies, What’s Virtusa doing on CD?
• Coming up next…
3

4. What is Continuous Delivery?

5. The Big Question - What does it take to get a
feature/hotfix/patch to your customer?
• What’s involved in doing a release?
• How long does it take?
• How many steps are involved?
• How successful is the process?
• How often do you do them?
• Do you have “heroes”?
• What would happen if a particular environment disappeared/melted down?
• Do your environments match?
• How quickly can you build an environment?
• How hard is it to do a patch? A major release?
5

6. 6
Courtesy - Web

7. 7
Courtesy - Web

8. Continuous Delivery
• 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.
• Your software is deployable throughout its lifecycle
• Your team prioritizes keeping the software deployable over working on
new features
• Anybody can get fast, automated feedback on the production readiness of
their systems any time somebody makes a change to them
• You can perform push-button deployments of any version of the software
to any environment on demand
Martin Fowler - http://martinfowler.com/bliki/ContinuousDelivery.html
8

9. I thought I knew CI, Agile, Quality and
DevOps!

10. CD Tag Cloud!
10

11. Audience Poll - 1
Who drives Continuous integration and
delivery in your project?
•DEV
•Operations
11

12. Audience Poll - 2
On average how frequently are changes integrated
into the release branch/trunk? (not the developer
feature/promo/task branch, but the main code line
from which a release candidate is built)
•daily
•weekly
•with each sprint
•only once feature development is complete
12

13. Audience Poll - 3
What latent code strategies have you used
within the last 12 months?
•None...SCM feature branching
•Hidden code
•Abstraction
•Feature toggles
13

14. Audience Poll - 4
Merge problems?
•None – We don’t do multiple releases and our single
release process has minimal merges whatsoever
•We don’t do multiple releases but our single release
process has merge issues
•Multiple releases – Merge issues
•Automated Merge process using SCM Streams and CI
automation
14

15. Quick Case Study
Etsy (Online retailer):
22+ million members
800,000+ active shops
18+ million items currently for sale
400+ employees
Business Problem - Our site is so successful, how
can we move fast enough to keep up with feature
demand?
15

16. We’re pretty Agile – Aren’t We?
*Etsy Scenario
16

17. We’re developers and we can solve any problem!
17

18. We own our stuff from cradle to grave!
18

19. We can absorb change with minimal impact!
19

20. We test our code – it always works in my local!
20

21. We don’t work on weekends!
21

22. We’re pretty Agile – Aren’t We?
22

23. Etsy - They’re pretty Agile!!!
23

24. Etsy - Continuous Deployment Math!
• N = # of deploys
• P = probability of site degradation
• S = average severity of degradation
• T = time to detect/resolve
Expected Downtime = N*P*S*T
24

25. Etsy - Release!!!
N = # of deploys
S = avg. severity of degradation
ED = Expected Downtime
P = prob. of degradation
T = time to detect/resolve
Before CD
N=1
P = 0.5
S = 0.7
T = 100
After CD
N = 250
P = 0.1
S = 0.05
T=5
E.D = 35
E.D = 6.25
25
*Arbitrary Numbers

26. 26

27. Continuous development, integration and the
ability to continuously release – The CD
Pipeline

28. Fundamental Prerequisites!
28
Agile Tools Integration, Aggressive Automation, Measurable continuous improvements

29. Design
3 inevitabilities we design for:
• Things break, unexpectedly
• What we’re building changes
• We don’t get to start over
29

30. Architectural Principles
Don’t bet against the future.
Our customers are humans.
Simplicity always wins, in the end.
Ambiguity kills momentum.
Make failure cheap.
Technical debt is an inevitable by-product of
shipping code.
Optimize for change.
30

31. Continuous Delivery Abstract model
31

32. Configuration Management
Version Everything!!!
• Single Identifier
• Dependencies
• App Configurations
• Data
• Environments
32

33. Continuous Integration (Build Pipeline)
•
•
•
•
•
•
•
•
Check-in Daily
Make Code Self Testing
Commit to Trunk
Automate the Build
Keep the Build Fast
Every Commit results in Build/Validate
Test in Clone of Production
Automate Deployments
33

34. Testing Quadrant
34

35. Testing Recommendations
• Automated Acceptance Tests
•
•
•
•
•
Fast Feedback
Reduce Tester workload
Testers can do Exploratory Testing
Regression Tests
Requirements can be generated from Tests
• Acceptance Test Approaches
• Acceptance Test Driven Development (ATDD)
• Behavior Driven Development (BDD)
Given [some precondition] When [some event] Then [some result]
35

36. Deployment Automation
36

37. Continuous Delivery Pipeline
37

38. Work, Gamified!

39. What’s next for Agile?
2001-2012
2012 onwards…
Continuous Integration, delivery,
design, feedback
Continuous play
Courtesy – Thoughtworks
39

40. So, what is Gamification?
Gamification is integrating game
thinking and design into activities to
increase engagement, learning and
fun.
40

41. Work, Gamified! Origin
41

42. Gamified development!
• Gamifying (Agile) Development –
• Stories, Narratives, Spikes
• Project initiation (iteration 0), technology discovery thru games
• Hackathons
• Gamify feature development [motivation, social, engaged, velocity, quality]
• Develop from Cradle to Grave – rewards for tdd, automation from dev to prod (making life easier,
process improvements)
• Progress, Rules and Social impact–
• TDD (rules), Kanban (visual), CI build monitors, Card Wall (visual)
• Socialize – Yammer, Project Dashboards, Leaderboard (Jenkins CI Game Plugin)
42

43. Metrics and Rewards!
• An integrated view of the development efficiency can be derived from usual metrics all along • SVN Metrics
• JIRA Metrics
• Code review metrics
• CI Metrics
• Deployment Metrics
• Automated unit/acceptance test metrics
• Is there a tool (or a set of tools integrated) that pulls out and then co-relates this information to
derive meaningful metrics?
43

44. How developers are
paid – Virtual Currency
44
Courtesy - Web

45. Metrics and Rewards…
Description
Reward Points
Check-in and build passes (with unit tests)
1
One or more unit tests failed
-10
Compiler error (come on now)
-20
Big check-in caused build to remain in a broken
state for hours
-40
Code review (complexity, re-use, leaks, copypaste)
-40
OthersJIRA metrics
Stack Exchange like metrics (Forums, QnA, tech discovery)
Continuous Improvement metrics (e.g. Maven build – time, accuracy, adherence to standards, Deployment
Engine metrics)
Jenkins - https://wiki.jenkins-ci.org/display/JENKINS/The+Continuous+Integration+Game+plugin
45

46. CD Tools, Products and Solutions out there!

47. CD Tools Matrix (Continuously evolving)
Version
Control
(SCM)
Dependency
Mgmt
DB mgmt
Infrastructure
Mgmt
CI
Build
Automation
Test
Deployment
Automation
ALM
Subversion
Nexus
Liquibase
Puppet
Hudson
Maven
Junit/jMock
/Mockito/D
bunit
XebiaLabs –
Deployit
Jira
Git
Artifactory
Flyway
Chef
Jenkins
Ant
Selenium/W
ebdriver
uDeploy (IBM
UrbanCode)
Bugzilla
Mercurial
Bamboo
Gradle
infinitest
ElectricCloud
– Electric
Commander
QC
Accurev
Teamcity
Buildr
Fitnesse
RebelLabs –
LiveRebel
Go
Jbehave/Cuc
umber
47

48. 48
Courtesy - Web

49. Coming up next…

50. QnA
Thanks!!!