SLIDE 1
Modern Continuous Delivery Modern Continuous Delivery
“ deploy to production
deploy to production from commit #1 from commit #1
SLIDE 2 Peter Bittner Peter Bittner
Developer Developer
- f people, companies and code
- f people, companies and code
@peterbittner, django@bittner.it behave-django pyclean djangocms-maps ansible-role-software django-probes django-apptemplates codeship-yaml django-organice PythonTurtle painless/tox django-bootstrap-static
SLIDE 3 Continuous Delivery Continuous Delivery
“ a set of practices and principles in software engineering
aimed at building, testing, and releasing software safely, faster, more frequently, and in a sustainable way.
Source: painless.software/continuous-delivery
SLIDE 4 Continuous Delivery Continuous Delivery
“ a set of practices and principles in software engineering
aimed at building, testing, and releasing software safely, faster, more frequently, and in a sustainable way.
“ the goal is to put the release schedule
in the hands of the business, not in the hands of IT.
Source: painless.software/continuous-delivery
SLIDE 5 Continuous Delivery Continuous Delivery
“ a set of practices and principles in software engineering
aimed at building, testing, and releasing software safely, faster, more frequently, and in a sustainable way.
“ the goal is to put the release schedule
in the hands of the business, not in the hands of IT.
Source: painless.software/continuous-delivery
?? ?? Continuous Continuous integration integration
SLIDE 6 Continuous Delivery Continuous Delivery
“ a set of practices and principles in software engineering
aimed at building, testing, and releasing software safely, faster, more frequently, and in a sustainable way.
“ the goal is to put the release schedule
in the hands of the business, not in the hands of IT.
Source: painless.software/continuous-delivery
?? ?? Continuous Continuous integration integration ?? ?? Continuous Continuous deployment deployment
SLIDE 7
Modern? Modern?
SLIDE 8
Modern? Modern?
Immutable infrastructure Immutable infrastructure
SLIDE 9
Modern? Modern?
Immutable infrastructure Immutable infrastructure Container orchestration Container orchestration
SLIDE 10
Modern? Modern?
Immutable infrastructure Immutable infrastructure Container orchestration Container orchestration Version control + automation Version control + automation
SLIDE 11
Modern? Modern?
Immutable infrastructure Immutable infrastructure Container orchestration Container orchestration Version control + automation Version control + automation Cloud-native applications Cloud-native applications
SLIDE 12
Choice or Lock-in? Choice or Lock-in?
SLIDE 13
- 1. Clean code
- 1. Clean code
- 2. Deploy to production
- 2. Deploy to production
from commit #1 from commit #1
There must be a better way! There must be a better way!
SLIDE 14
Demo Demo
SLIDE 15
Responsibility Layers Responsibility Layers
SLIDE 16
Responsibility Layers Responsibility Layers
Application Application
SLIDE 17
Responsibility Layers Responsibility Layers
Application Application Development Development
SLIDE 18
Responsibility Layers Responsibility Layers
Application Application Development Development Deployment Deployment
SLIDE 19
Responsibility Layers Responsibility Layers
Application Application Development Development Deployment Deployment Automation Automation
SLIDE 20 Application Application
One environment! 12-factor app. Build with features. Compose in environments.
1
SLIDE 21 Development Development
Make it easy! Standard practices. No comprehensive instructions. Simple & user-friendly!
3
SLIDE 22 Deployment Deployment
Make it beautiful! Easy to explain. Generate + seal your secrets,
- r seal + commit your secrets.
2
SLIDE 23 Automation Automation
Keep it simple! What you would do manually. Tell a story! ASAP
4
SLIDE 24
ASAP! ASAP!
as simple as possible as simple as possible
SLIDE 25 Deploy to production! Deploy to production!
- ften + from commit #1
- ften + from commit #1
SLIDE 26
Iterate! Iterate!
... and improve ... and improve
SLIDE 27
Agile, please. Agile, please.
test-driven, pair-programming test-driven, pair-programming
SLIDE 28
Free your software Free your software
no secrets, no security holes no secrets, no security holes
SLIDE 29 “ The only way to go fast
The only way to go fast is to go well. is to go well.
Source: , 2015 Technology and Friends, Episode 354
SLIDE 30 Thank you! Thank you!
for your precious time for your precious time
Painless Software Painless Software
Less pain, more fun.
SLIDE 31 Beautiful is better than ugly. Explicit is better than implicit. Simple is better than complex. Complex is better than complicated. Flat is better than nested. Sparse is better than dense. Readability counts. Special cases aren't special enough to break the rules. Although practicality beats purity.
Pythonistas Oath Pythonistas Oath
1
SLIDE 32 Errors should never pass silently. Unless explicitly silenced. In the face of ambiguity, refuse the temptation to guess. There should be one only one obvious way to do it. Although that way may not be obvious at first sight.
Pythonistas Oath Pythonistas Oath
2
SLIDE 33 Now is better than never. Although never is often better than *right* now. If the implementation is hard to explain, it's a bad idea. If the implementation is easy to explain, it may be a good idea.
Pythonistas Oath Pythonistas Oath
3
SLIDE 34 Continuous delivery is a honking great idea. If you deploy to production from commit #1. Let's do it! I start today.
Pythonistas Oath Pythonistas Oath
4
Python
