Your SlideShare is downloading. ×
0
Continuous Delivery
Leonardo Gamas
Software Engineer @ JusBrasil
http://www.jusbrasil.com.br
@leogamas
READ
THE
FUCKING
BOOK!!!
The Problem of Delivering
Software
Agile Manifesto
“Our highest priority is to satisfy the
customer through early and
continuous delivery of valuable
softwar...
Ask this
“If somebody thinks of a good idea,
how do we deliver it to users as quickly
as possible?”
Continuous Delivery, b...
Or ask this
“How long would it take your
organization to deploy a change that
involved just one single line of code?
Do yo...
Building the right thing (avoid waste)
Lean Startup Cycle
Reduce risk of release
Real project progress
Don’t deploy software manually
Don’t deploy to a production-like environment
only after development is complete
Don’t do manual configuration management of
production environments
Configuration Management
If something goes really wrong, how much
time to restore production?
Keep Everything in Version Control
Continuous Integration
Every Check-in Leads to a Potential Release
The Deployment Pipeline
Blue-green deployment
Canary release
Deployed != Released
Feature flags
Dev x Ops
DevOps
Questions?
References
● http://www.continuousdelivery.com/
● http://martinfowler.com/
● Continuous Delivery: Reliable Software Releas...
Continuous delivery
Continuous delivery
Continuous delivery
Continuous delivery
Continuous delivery
Upcoming SlideShare
Loading in...5
×

Continuous delivery

272

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
272
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Continuous delivery"

  1. 1. Continuous Delivery Leonardo Gamas Software Engineer @ JusBrasil http://www.jusbrasil.com.br @leogamas
  2. 2. READ THE FUCKING BOOK!!!
  3. 3. The Problem of Delivering Software
  4. 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. 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. 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. 7. Building the right thing (avoid waste)
  8. 8. Lean Startup Cycle
  9. 9. Reduce risk of release
  10. 10. Real project progress
  11. 11. Don’t deploy software manually
  12. 12. Don’t deploy to a production-like environment only after development is complete
  13. 13. Don’t do manual configuration management of production environments
  14. 14. Configuration Management
  15. 15. If something goes really wrong, how much time to restore production?
  16. 16. Keep Everything in Version Control
  17. 17. Continuous Integration
  18. 18. Every Check-in Leads to a Potential Release
  19. 19. The Deployment Pipeline
  20. 20. Blue-green deployment
  21. 21. Canary release
  22. 22. Deployed != Released Feature flags
  23. 23. Dev x Ops
  24. 24. DevOps
  25. 25. Questions?
  26. 26. References ● http://www.continuousdelivery.com/ ● http://martinfowler.com/ ● Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Jez Humble, David Farley. 2010
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×