Download as PDF, PPTX
More Related Content
Similar to Continuous integration with docker, buildbot and git
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Continuous integration with docker, buildbot and git
- 1. Continuous Integration with Docker,Buildbot and Git
- 2. About Me ● Pythonuser since 2007 ● Build web based systems using Python + Django mostly ● Gain interests in infrastructure gradually ● Start to build my own software company recently twitter: @adieu github: github.com/adieu website: www.adieu.me
- 3. Quiz ● ● ● ● ● How many ofyou know Docker How many of you know Buildbot How many of you know Git How many of you deploy software to servers How many of you have any kinds of experience with virtualization
- 4. Continuous Integration with Docker,Buildbot and Git
- 5.
- 6. Why it matters ●More and more integration points in modern software system ● Successful deployment became a challenge ● Catch the bug before it hits production ● DevOps and DRY ● Knowledge is kept by source code instead of human brain
- 7. Continuous Integration with Docker,Buildbot and Git
- 8.
- 9.
- 10. Why it matters ●Thin layer above the hardware provides a fast and unified environment ● Program runs in an isolated container with resource and network control ● Easy to use CLI and remote api ● One image could been built from a Dockerfile and runs on multiple machines
- 11. Continuous Integration with Docker,Buildbot and Git
- 12.
- 13. Why it matters ●Highly customizable ● Lightweight but battery included ● All configuration could be kept in the source code so that version control works ● It’s Python!
- 14. Continuous Integration with Docker,Buildbot and Git
- 15.
- 16. Why it matters ● ● ● ● Theversion control system that works Fast and efficient Suitable for collaboration workflow Common choice by the open source community ● Github!
- 17. Build a Programmable SoftwareCompany A Case Study
- 18.
- 19.
- 20.
- 21. The Problem ● Noversion history ● Only server admin could deploy ● Have to setup development environment to run tests locally ● No deploy history ● Does not work well with multiple repositories ● Non-isolated build environment
- 22. Git + Fabric gitpush Local post-update Git Fabric
- 23. The Problem ● Noversion history ● Only server admin could deploy ● Have to setup development environment to run tests locally ● No deploy history ● Does not work well with multiple repositories ● Non-isolated build environment ● Hard to setup
- 24. Git + Buildbot gitpush Local webhook Git Buildbot
- 25. The Problem ● Noversion history ● Only server admin could deploy ● Have to setup development environment to run tests locally ● No deploy history ● Does not work well with multiple repositories ● Hard to setup ● Non-isolated build environment ● Complex build steps ● Non-repeatable deploy workflow
- 26. Git + Buildbot+ Docker git push Local webhook Git Docker Buildbot http api
- 27.
- 28.
- 29. Benefits ● Each servicehas its own git repo and runs in a docker container ● Every change is kept track of by git ● Once receiving the change, buildbot will run tests, build a new docker image, stop the old container and start a new one with the newly built image ● The whole system is like a program, one could change a service by modifying the source code of its image ● Empower everyone to change everything
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.