Continuous Integration,

Delivery and Deployment

https://en.wikipedia.org/wiki/System_integration

23/11/15
2
Software Integration
•  System Integration
•  Change Integration: Merging

Possible integration conflict!

23/11/15
3
Integration Conflicts
•  Merge Conflicts
•  Detected by version control software
•  Semantic Conflicts
•  Detected by compiler, tests and code review

http://martinfowler.com/bliki/SemanticConflict.html

23/11/15
4
Regression Testing
The purpose of regression testing is to ensure that changes have
not introduced new faults.

Experience has shown that as software is changed, emergence of

https://en.wikipedia.org/wiki/Regression_testing

23/11/15
5
History of Software Integration and
Regression Testing
•  Prehistory: Big Bang Integration
•  1996: Daily Build and Smoke Test (Steve McConnell)
•  2000: XP and Continuous Integration (Kent Beck)
•  2006: Continuous Integration (Martin Fowler)
•  2009: Continuous Deployment (Timothy Fitz)
•  2010: Continuous Delivery (Jez Humble & David Farley)
•  2012: Experiment System (Holmström Olsson et al.)

23/11/15
6
Big Bang Integration
•  System Integration
•  Develop subsystems independently, integrate when ready
•  Change Integration
•  Develop changes in branches, merge when ready

23/11/15
7
Big Bang Integration
“We entered a huge depressing warehouse stacked full with cubes.
I was told that this project had been in development for a couple of
years and was currently integrating, and had been integrating for
several months.
My guide told me that nobody really knew how long it would take to
finish integrating.
From this I learned a common story of software projects: integration
is a long and unpredictable process.”

http://www.martinfowler.com/articles/continuousIntegration.html

23/11/15
8
Big Bang Integration
•  Development is simple, because nothing is changing
•  Integration is complex and takes unpredictable time

23/11/15
9
23/11/15
10
1996: Daily Build and Smoke Test
•  Build and smoke test the whole software system daily
•  Fix broken builds
•  “Integrate… usually once every few days”

McConnell, S., 1996. Daily build and smoke test. IEEE software 143–144.

23/11/15
11
Daily Build and Smoke Test
•  Minimizes integration and low quality risk
•  Easier defect diagnosis developed
•  Improved morale verified
Big Bang Daily

code

risk

time

23/11/15
12
Daily Build and Smoke Test
•  Context of large systems
•  Tests allowed to take multiple hours
•  Timed builds
•  Smoke tests evolve when the system evolves
•  Dedicated roles take care of the build

23/11/15
13
Daily Build and Smoke Test
“The smoke test should be thorough enough that if the build
passes, you can assume that it is stable enough to be tested more
thoroughly.”

“The standard needs to set a quality level that’s strict enough to keep
showstopper defects out but lenient enough to disregard trivial
defects, an undue attention to which could paralyze progress.”

23/11/15
14
2000: Extreme Programming
•  Holistic software development
methodology
•  Continuous Integration, one of the many
practices

Beck, K., 2000. Extreme programming explained: embrace change. Addison-Wesley

23/11/15
15
Extreme Programming and Continuous
Integration
“No code sits unintegrated for more than a couple of hours.”

“At the end of every development episode, the code is integrated and
all the tests must run at 100%.”

“You need a reasonably complete test suite that runs in a few

23/11/15
16
Continuous Integration

pass

Develop Integration & Testing

fail

Fix broken build

23/11/15
17
2006: Continuous Integration Extended
•  Single source repository
•  Integration machine
•  Fix broken builds immediately
•  Keep the build fast (10 minutes)
•  Test in a clone of the production environment
•  Automate deployment

http://www.martinfowler.com/articles/continuousIntegration.html

23/11/15
18
2009: Continuous Deployment
“The high level of our process is dead simple: Continuously
integrate (commit early and often). On commit automatically run all
tests. If the tests pass deploy to the cluster. If the deploy succeeds,
repeat.”

http://timothyfitz.com/2009/02/08/continuous-deployment/
http://timothyfitz.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/

23/11/15
19
Continuous Deployment
“So what magic happens in our test suite that allows us to skip
having a manual Quality Assurance step in our deploy process?
The magic is in the scope, scale and thoroughness. It’s a thousand
test files and counting. 4.4 machine hours of automated tests to be
exact.”

“Great test coverage is not enough. Continuous Deployment requires

23/11/15
20
Continuous Deployment
•  Context of cloud systems
•  Problems in production will always happen
•  How to mitigate the problems?
•  Smaller releases have smaller scope and are easier to debug
•  Automated deployments allow fast fixing
•  Deploy to a subset of users first to mitigate problem scope
•  Production can be monitored and reverted automatically

23/11/15
21
Continuous Deployment
•  Minimizes release risk developed
•  Easier defect diagnosis verified
•  Improved morale released

Frequent Frequent
verification release

code

risk

time

23/11/15
22
2010: Continuous Delivery
•  Every change should be releasable…
•  ...but not necessarily released
automatically
•  Allows human verification

Humble, J., Farley, D., 2010. Continuous Delivery: Reliable Software Releases through
Build, Test, and Deployment Automation. Addison-Wesley Professional.

23/11/15
23
Continuous Delivery
Deployment Pipeline

23/11/15
24
Continuous Delivery

23/11/15
25
Continuous Delivery
You’re doing continuous delivery when:
•  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

http://martinfowler.com/bliki/ContinuousDelivery.html

23/11/15
26
2012: Experiment System

R&D as an
Experiment
System
Continuous
Deployment
Continuous
Integration
Agile R&D
Organization
Traditional
Development

Olsson, H.H., Alahyari, H., Bosch, J., 2012. Climbing the “Stairway to Heaven” – A Multiple-Case Study
Exploring Barriers in the Transition from Agile Development Towards Continuous Deployment of Software, in:
Proceedings of the 2012 38th Euromicro Conference on Software Engineering and Advanced Applications.
Washington, DC, USA, pp. 392–399.

23/11/15
27
Experiment System
“actual deployment of software functionality is seen as a way of
experimenting and testing what the customer needs”

•  Beyond regression testing and integration

23/11/15
28
Delivery Activities

Develop Integrate QA Release

23/11/15
29
Waterfall

Develop Integrate QA Release

23/11/15
30
Continuous Integration

Develop + Integrate QA Release

23/11/15
31
Continuous Delivery

Develop + Integrate + QA Release

23/11/15
32
Continuous Deployment

Develop + Integrate + QA + Release

23/11/15
33
Practitioner surveys

•  2015 State of DevOps Report

https://puppetlabs.com/2015-devops-report
http://info.thoughtworks.com/Continuous-Delivery-Maturity-Model.html

23/11/15
34
Survey: deployment frequency

23/11/15
35
Survey: deployment lead time

23/11/15
36
Survey: practices

http://info.thoughtworks.com/Continuous-Delivery-Maturity-Model.html

23/11/15
37
Survey: barriers

http://info.thoughtworks.com/Continuous-Delivery-Maturity-Model.html

23/11/15
38
Problems when adopting continuous
delivery
•  Build design
•  Complex build, inflexible build
•  Product design
•  Modularization, internal dependencies, database schema changes, unsuitable architecture
•  Integration
•  Large commits, broken build, merge conflicts, work blockage, long-running branches…
•  Testing
•  Ambiguous test result, flaky tests, untestable code, time-consuming testing, UI testing…
•  Release
•  Customer data preservation, documentation, feature discovery, marketing, more deployed bugs
•  Human & Organization
•  Lack of discipline, more pressure, lack of motivation, lack of experience, team coordination…
•  Resources
•  Effort, insufficient hardware resources, network latencies

Laukkanen, E., Itkonen, J., Lassenius, C., 2015. Problems, Causes and Solutions When Adopting Continuous Delivery - A Systematic
Literature Review. Manuscript in preparation.

23/11/15
39
Problems are connected

Laukkanen, E., Itkonen, J., Lassenius, C., 2015. Problems, Causes and Solutions When Adopting Continuous Delivery - A Systematic
Literature Review. Manuscript in preparation.

23/11/15
40
What to consider
•  Value of fast release cycle
•  Competitive market
•  Product ambiguity
•  Cost of fast release cycle
•  Competences, legacy code, infrastructure, maintenance
•  How often can you release
•  Cost of release
•  How long can quality assurance take
•  Cost of production bugs

23/11/15
41
Thanks!
[email protected]