Continuous Integration & Automated Builds with Docker

A short talk on CI using Github, Drone.io & Docker Hub Automated Build. Presented on 15th October on the 1st Singapore Docker meetup at Viki Inc.

Transcript

1. CONTINUOUS INTEGRATION AND AUTOMATED BUILDS WITH DOCKER Fadhli Rahim @_fadhli Viki Inc
2. WE ALL TEST CODE (I hope you do)
3. WE ALL SHIP CODE (since all our test pass)
4. ! WHY DOCKER?
5. – everyone “It works on my machine!”
6. • Straight forward • Dockerfile • Build an image, deploy that image
7. • Repeatable • Exact same image can be deploy to multiple machines
8. CI & DOCKER • Drone.io • Circle CI • shippable.com
9. WHAT IS DRONE? • https://drone.io/ • https://github.com/drone/drone • SaaS or Self Hosted • Written in Go • Uses docker to run/test build
11. HOW DOES IT WORK? • watches git repo `.drone.yml` file • clones your repo after git push • creates docker image
12. • runs your test script • post notification • webhooks
13. image: bradrydzewski/ruby:2.0.0 services: - postgres:latest - redis script: - cp config/database.yml.drone config/database.yml - bundle install - psql -c 'create database app_test;' -U {{DB_USER}} -h {{DB_HOST}} -p {{DB_PORT}} - bundle exec rake db:schema:load - bundle exec rspec . notify: email: recipients: - fadhli@viki.com webhook: on_success: true on_failure: false urls: - https://registry.hub.docker.com/u/viki/baboon/trigger/access_token/ hipchat: room: 1 token: token on_started: true on_success: true on_failure: true .drone.yml
14. DOCKER HUB AUTOMATED BUILDS • when you’re tired of manually docker building & push • a simple git push to github • builds your docker image base on your Dockerfile
15. can be configured to build git branch or git tag
16. docker tags helps differentiate build and deployments
17. MY WORKFLOW git push github drone.io docker hub - git clone viki/app - docker build test - run test - docker build - docker push
18. THINGS TO IMPROVE • Faster build (drone/docker hub) • Simplify workflow. Have drone.io configured to pull from docker hub and run specs. • Continuous deployment
19. Q & A