During this talk, I’ll start by introducing continuous delivery and I will distinguish Continuous Integration from Continuous Delivery, why teams need to do continuous delivery and what is required for teams to do it. I’ll then present the principles and practices involved in continuous delivery along with the benefits in general and on a personal basis from my operations. Finally, I will wrap the talk up with a demo using one of the projects where I have used Continuous Delivery.

1. The Transition from Continuous Integration to continuous Delivery
Joannah Nanjekye
nanjekyejoannah@gmail.com
@JoannahNanjekye
Geek night kampala

2. ● Joannah Nanjekye
● Programmer , Fintech Uganda Limited
● .Net and Ruby.
● Interests
systems programming
About me

3. Outline
● Overview of CI
● Continuous delivery
● Demo

4. what is continous integration
Continuous Integration is a software development practice where members of a team integrate their work frequently,
usually each person integrates at least daily - leading to multiple integrations per day
http://www.martinfowler.com/articles/continuousIntegration.html

5. A Typical CI workflow

6. The last mile to a release
last mile

7. The last mile
“It is hard enough for software developers to write code that works on their
machine.But even when thats done,there is a long journey from there to
software that is producing value since software only produces value when its in
production.”
Martin Fowler

8. Release management Antipatterns
● Manual deployments
● Wait until development is done to release.
● Manual configuration management.

10. There is need for repeatable,reliable and reusable way of ensuring reliable
releases;

11. Continuous Delivery

12. ...a set of practices to software delivery that aims at
building software so that it is in a state where it could be in
production or is releasable at any time ...
What is continous delivery..

13. Goal
● High Quality releases
● Low cycle time

14. Continuous delivery setup

15. You are doing CD when….
● Your software is deployable throughout its lifecycle
● Team Priority is having deployable software 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

16. Continous what????

17. what is required to do CD
● Automation of the delivery process.
○ Automated testing
○ Continuous integration
○ Automated deployment
● The ‘DevOps’ culture of delivery.

18. Benefits of Continuous delivery
● Making release a non-issue.
● Faster Feedback .
● Believable progress.
● Accelerated time to market.

19. challenges
● Automated tests
● Developer training
● Incremental releases are complicated.

20. Demo

22. Thank you