The document discusses continuous deployment, which is a software engineering approach where teams continuously produce valuable software in short cycles and ensure it can be reliably released at any time. Continuous deployment provides benefits like less queues, faster bug fixes, better developer satisfaction and recruitment, and higher quality through more testing. It recommends setting up continuous integration servers to automatically build, test, and deploy code changes to production as they are integrated and passing tests. Feature branches and centralized workflows can help manage conflicts between developers. Monitoring is also important for continuous deployment.

1. How to deploy to production
10 times a day
Andrii Shumada
Ciklum/e-conomic
eagleeye
eagleeye_s
eagleeyes91@gmail.com

2. What is contious deployment?
A software engineering approach in which teams keep producing
valuable software in short cycles and ensure that the software can
be reliably released at any time

3. Why to do Continuos deployment?

4. less queues
no waiting till next
scheduled realease
more tasks get done
Speed

5. Developer satisfaction
code with feauture is isolated
less planings
less stress

6. Quality
Bugs can be found faster
Bugs can be fixed faster
More concentrated testing
Less risks

7. Recruitment
Hey, we deploy every day!

8. echo alias deploy=’mocha && git push heroku master‘ >> ~/.bash_profile
Let’s setup super simple CD

9. How about confilcts with other guys?

10. Centralized Workflow

11. Feature Branch Workflow

12. Manual testing
(before) Prod
Staging

13. Manual testing
(after) Prod
Staging-feature-1
feature-branch-1
Staging-feature-2
feature-branch-2
Staging-feature-3
feature-branch-3

14. Contious integration server
1.Trigger rules 2.Build steps
Checks VCS
by user
deploy
TeamCity
Jenkins
Shippable
Travis
run tests
Web hooks

15. Safe merge to master
and deploy
Production
CI server
Write your
feature
Push your
feature to
branch
ready/feature1
delete ready/feature1
branch
deploy
master
pulls master locally
merge ready/feature1 to
master locally
run tests
push to origin/master

16. When we can release that?
PO/Manage
(before)

17. Is it in production?
PO/Manager
(after)

18. Demo

19. Don’t forget about monitoring
General recomendations
Split big tasks to fit 1-2 days
release cycle
Don’t plan and estimate

20. Useful links
https://github.com/mafintosh/hms
https://github.com/progrium/dokku
https://github.com/e-conomic/tcmerge
https://waffle.io
https://travis-ci.org
eagleeye
eagleeye_s
eagleeyes91@gmail.com