Continuous Delivery overview

1. Continuous Delivery

2. Rob Spieldenner
software developer at Next Century Corporation
@robspieldenner
rob.spieldenner@gmail.com
github.com/rspieldenner

3. Our highest priority is to
satisfy the customer
through early and
continuous delivery of
valuable software.
from “the agile manifesto”

4. How long would it take your
organization to get a single
line change into production?

5. Invent the Future

6. Create awesome
software that does
what the customer
wants

7. Eliminate Test-Fix-Test

8. Make Releases
Non-Events

9. Avoid Firedrills

10. Continuous Integration
Continuous Delivery
Continuous Deployment

11. Outline
Build Pipeline
Less Fragile Automated Acceptance Tests
Infrastructure as Code

12. The Build Pipeline

13. Version Control
Manual
Automated
Tests
Acceptance
Automated
Tests
Commit Acceptance Deploy to
Automated Signoffs
Stage Tests Production
Acceptance
Tests Other Tests
Artifact
Repository

14. Version Control
&
Artifact Repository

15. What goes in version control?

16. Everything

17. Everything
that can’t be rebuilt

18. What goes in the artifact
repository?

19. binary output from the builds
libraries pulled through gradle/ivy/maven
base vm images
apt/yum repositories
application installers/bundles

20. Version Control
Manual
Automated
Tests
Acceptance
Automated
Tests
Commit Acceptance Deploy to
Automated Signoffs
Stage Tests Production
Acceptance
Tests Other Tests
Artifact
Repository

21. The Commit Stage

22. continuous integration plus

23. Static Analysis
findbugs
codenarc
sonar
checkstyle

24. build binaries once

25. keep the runtime short

26. Version Control
Manual
Automated
Tests
Acceptance
Automated
Tests
Commit Acceptance Deploy to
Automated Signoffs
Stage Tests Production
Acceptance
Tests Other Tests
Artifact
Repository

27. Automated Acceptance
Tests

28. executable specifications

29. write in domain language

30. Cucumber Example
Feature: Search courses
In order to ensure better utilization of courses
Potential students should be able to search for courses
Scenario: Search by topic
Given there are 240 courses which do not have the topic "biology"
And there are 2 courses A001, B205 that each have "biology" as one of the
topics
When I search for "biology"
Then I should see the following courses:
| Course code |
| A001 |
| B205 |
https://github.com/cucumber/cucumber/wiki/

31. parallelize

32. why automated?

33. having humans perform repetitive,
scripted manual tests is wasteful

34. need quick feedback to always be
ready to deliver

35. avoid test-fix-test “last mile”

36. Version Control
Manual
Automated
Tests
Acceptance
Automated
Tests
Commit Acceptance Deploy to
Automated Signoffs
Stage Tests Production
Acceptance
Tests Other Tests
Artifact
Repository

37. Manual Testing

38. exploratory testing

39. UI check

40. sprint/customer demos

41. your technical debt ...

42. your technical debt ...
non-automated acceptance tests

43. Version Control
Manual
Automated
Tests
Acceptance
Automated
Tests
Commit Acceptance Deploy to
Automated Signoffs
Stage Tests Production
Acceptance
Tests Other Tests
Artifact
Repository

44. Other Testing

45. performance testing

46. capacity testing

47. security testing

48. Version Control
Manual
Automated
Tests
Acceptance
Automated
Tests
Commit Acceptance Deploy to
Automated Signoffs
Stage Tests Production
Acceptance
Tests Other Tests
Artifact
Repository

49. Optional Signoffs

50. Version Control
Manual
Automated
Tests
Acceptance
Automated
Tests
Commit Acceptance Deploy to
Automated Signoffs
Stage Tests Production
Acceptance
Tests Other Tests
Artifact
Repository

51. On-Demand
Deployment

52. deploy to dev, test, production
same

53. apply different configurations

54. Version Control
Manual
Automated
Tests
Acceptance
Automated
Tests
Commit Acceptance Deploy to
Automated Signoffs
Stage Tests Production
Acceptance
Tests Other Tests
Artifact
Repository

55. Path to Continuous
Delivery

56. version control
and
automated build

57. automated deployment scripts

58. cleanup builds to extract
configuration

59. automated acceptance tests

60. automate infrastructure

61. Outline
Build Pipeline
Less Fragile Automated Acceptance Tests
Infrastructure as Code

62. Less Fragile Automated
Acceptance Tests

64. Write Tests at the Domain Level

65. Page Object Model

66. Geb Page Objects
import geb.Page
class LoginPage extends Page {
static url = "http://myapp.com/login"
static at = { heading.text() == "Please Login" }
static content = {
heading { $("h1") }
loginForm { $("form.login") }
loginButton(to: AdminPage) { loginForm.login() }
}
}
class AdminPage extends Page {
static at = { heading.text() == "Admin Section" }
static content = {
heading { $("h1") }
}

67. Test Code Using Geb Page Objects
import geb.Browser
Browser.drive {
to LoginPage
assert at(LoginPage)
loginForm.with {
username = "admin"
password = "password"
}
loginButton.click()
assert at(AdminPage)
}

68. Cucumber/EasyB Acceptance tests
abstraction layer (Page Objects,
Window Driver)
application

69. Outline
Build Pipeline
Less Fragile Automated Acceptance Tests
Infrastructure as Code

70. Infrastructure as Code

71. Benefits
Configuration Management via version control
can rebuild exact infrastructure for any
point in project history
no unique snowflakes
DevOps

73. chef example
package "ntp" do
action [:install]
end
ntp_server = data_bag_item('ntp', 'default_server')
template "/etc/ntp.conf" do
source "ntp.conf.erb"
variables( :ntp_server => ntp_server['value'] )
notifies :restart, "service[ntpd]"
end
service "ntpd" do
action[:enable,:start]
end

74. virtualization

75. virtualbox and vagrant

76. veewee to create OS base image

77. chef or puppet
to describe each system

78. vagrant
to manage vms on dev machines

79. Notional Environment
Multiple clusters networked together in a
distributed workflow
A cluster is
one server with jboss for the application
one database server
one server for ldap and nagios

80. Setup base vm - Ubuntu 12.04
Create Chef recipes for server components
rpm packages(w/versions)
jdk 7, jboss
oracle

81. Create overarching Chef recipe
one per server
applies lower level/reusable recipes
Setup cluster in vagrant

82. Other Techniques

83. Branch by Abstraction

84. Feature Toggles

85. Zero Downtime Deploys

86. Blue Green Deploys

87. Project Immune System

88. Database Versioning

91. Resources
http://refcardz.dzone.com/refcardz/
continuous-delivery-patterns
http://continuousdelivery.com/
http://www.infoq.com/author/Jez-Humble
http://continuous-delivery.thoughtworks.com/
http://devopscafe.org/

92. Resources
vagrantup.com
cukes.info
www.gebish.org
www.opscode.com/chef
puppetlabs.com