Creating a Continuous Delivery Pipeline with Docker Three different ways! (time permitting)
Time to get on the same page
What the heck is Continuous Deployment?
</> SCM BUILD DEPLOY
Write code Push to repo Build / Test Deploy to servers
What are some of the benefits of CD?
● Repeatable process● Automatically run tests● Automatically deploy new code to servers● No manual steps need to be taken● Shorter deployment cycles● Scales with your dev team as it grows
What are some of the challenges of CD?
● Deciding on which tools are right for you or right for the specific job
● Wiring everything up so it works together● Getting people on your team to stop doing
things manually● Writing tests for all of your code● What other challenges have you run into?
Continuous Deployment Requires Automation - SCM
Continuous Deployment Requires Automation - Builds
Continuous Deployment Requires Automation - Deployments
… continued
Method #1● DockerHub Automated Build ● DockerHub Webhook Deployment● ContainerShip Webhook-Receiver
Method #2● TravisCI Image Build● TravisCI Push Image to DockerHub● TravisCI curl to ContainerShip API
Method #3
Github Webhook & Jenkins
Resources
Git Repo:
https://github.com/containership/ci-demo
Pluggable webhook receiver:
https://github.com/containership/webhook-receive
ContainerShip:
https://containership.io
Top Related