2014 was the year of Docker. The container-based world exploded on the scene with the promise to reinvent how you think about distributed applications. But is it just hype or are there immediate benefits to be realized? Join us to explore Continuous Integration/Continuous Delivery leveraging containers, one of the early use cases proving successful with Docker, resulting in reduced Dev/Test cycle times and lower infrastructure costs. We'll walk through the end-to-end CI/CD workflow, highlighting the big wins containers have introduced, as well as discuss common challenges to avoid. Lastly, we'll look ahead, identifying the next set of use cases to likely achieve real-world benefits from containers.
29. devops is culture, so to make it a
application
delivery
pipelines
F
A
C
rictionless
gile
ontinuous
ransparent
T
30. Transparency
if you want to do just 1 thing this year
every action
• starts in a
chat room
• tracked as a
github issue
• ends in a
chat room
31. Transparency
if you want to do just 1 thing this year
business req
support
prod errors
every action
• starts in a
chat room
• tracked as a
github issue
• ends in a
chat room
32. Continuous
• continuous integration for every pull-request
• 1 step docker build image for every merge to
`master`
• 1 step auto deploy & continuous functional
testing
• deployment to prod is just changing an ENV var
33. Agile
• no SSH!
• bug fixes, new changes, ops scripts all go the same way
• always deployable `master`
• no feature branching
• feature flags
• in-code branching
• small frequent changes
• beta program