1. Continuous Delivery
Leonardo Gamas
Software Engineer @ JusBrasil
http://www.jusbrasil.com.br
@leogamas

2. READ
THE
FUCKING
BOOK!!!

3. The Problem of Delivering
Software

4. Agile Manifesto
“Our highest priority is to satisfy the
customer through early and
continuous delivery of valuable
software.”
http://agilemanifesto.org/principles.html

5. Ask this
“If somebody thinks of a good idea,
how do we deliver it to users as quickly
as possible?”
Continuous Delivery, by Jez Humble and David Farley

6. Or ask this
“How long would it take your
organization to deploy a change that
involved just one single line of code?
Do you do this on a repeatable, reliable
basis?”
Mary and Tom Poppendieck book "Implementing Lean
Software Development"

7. Building the right thing (avoid waste)

8. Lean Startup Cycle

9. Reduce risk of release

10. Real project progress

11. Don’t deploy software manually

12. Don’t deploy to a production-like environment
only after development is complete

13. Don’t do manual configuration management of
production environments

14. Configuration Management

15. If something goes really wrong, how much
time to restore production?

16. Keep Everything in Version Control

17. Continuous Integration

18. Every Check-in Leads to a Potential Release

20. The Deployment Pipeline

24. Blue-green deployment

25. Canary release

26. Deployed != Released
Feature flags

28. Dev x Ops

29. DevOps

30. Questions?

31. References
● http://www.continuousdelivery.com/
● http://martinfowler.com/
● Continuous Delivery: Reliable Software Releases
through Build, Test, and Deployment Automation. Jez
Humble, David Farley. 2010