Using Docker to Develop, Test and Run Maven Project

My Talk on JFall 2014 (Netherlands) on using docker for development and testing.

Transcript

1. Using Docker to Develop, Test and Run Maven Projects Wouter Danes ING
2. Full Stack Engineer @wouterdanes github.com/wouterd wouterdanes.net
3. Agenda • What is docker? • Ways I use Docker for Development • Using Docker to Scale CI • Integrating Docker in your Build Process • Demo app • Wouldn’t it be great if..
4. What is docker?
5. Hai, Can I Has Rootz?
6. What is docker? Virtual Machines Docker Containers
7. Ways I use docker during development
8. Shadow IT
9. Run “production” locally
10. Proofs of Concept
11. Using Docker to Scale CI • Spawn build slaves • No port collisions • Master only development • No version / stack collisions in “environment”
13. Integrating Docker in your Build Process
14. build test package test package publish High level build process
15. build test package test package publish build run start stop link expose tag push Docker commands per build step
16. build test package test package publish build run start stop link expose tag push resources compile test package integration- test verify install deploy Maven vs Docker
17. Docker Maven Plugin Zoo • 12 github projects • Varying focus, some better than others • pick the one that best fits your purpose • Some interesting ones: – wouterd/docker-maven-plugin – rhuss/docker-maven-plugin – spotify/docker-maven-plugin – rhuss/docker-maven-plugin
18. What should a maven plugin do? • Build docker images • Start containers • Link containers • Wait for containers to finish initialisation • Expose URLs / port info to integration tests • Clean up • Push images to an index / registry
19. Demo project
20. Wouldn’t It Be Great If.. • Every team would publish – Application images – Application test images – Something describing their dependencies – Or maybe an image that builds their environment?
24. Wouldn’t It Be Great If.. • Every team would publish – Application images – Application test images – Something describing or creating their dependencies • And then you could: – Auto-test against new dependencies? – Auto-test dependants vs your new version?