How to organize and automate process of Continuous Delivery

1. How to deploy to production
10 times a day
Andrii Shumada
Sr. Software Developer at
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 release
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. When we can release that?
PO/Manager
(before) (after)
Is it in production?

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

16. 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

17. Create branch and pull requst
Usage: prod ‘valid-branch-name’

18. tcmerge (client-side)
Creating ready branch
https://github.com/debitoor/tcmerge
# find current branch name
currentBranch=`git rev-parse --abbrev-ref HEAD`
#push current branch to
readyBranch = ready/$currentbranch/$timestamp
git push origin $currentBranch:$readyBranch

19. teamcity-merge - TeamCity side

20. Demo

21. - Split big tasks to fit 1-2 days
release cycle
- Split application to services

22. Don’t plan and estimate

23. Remember about monitoring

24. Useful links
https://github.com/progrium/dokku
https://github.com/debitoor/tcmerge
https://github.com/debitoor/teamcity-merge
https://waffle.io
https://travis-ci.org
https://hub.github.com/
eagleeye
eagleeye_s
eagleeyes91@gmail.com