The previous posts in this series on Docker have looked at running containers to run services, specifically a web server and database server. However, Docker allows containers to be created, run, stopped and destroyed so cheaply that they can be used to run a single job. This job could be a script or even a single command. Unlike a service, a job will stop running when it’s complete. A container running a short lived job can be set to automatically stop and remove itself once the job is complete. If the job needs to be run again, it is reasonably efficient for Docker to start up a brand new container as required.
Stuart 'Stevie' Leitch's blog on Software Development, Java Technologies, Security and Testing
Tagsapm appdynamics archetype blame bug ci container DBUnit deploy docker Dockerfile Docker Hub github hibernate image integration test jetty junit maven microservice mistake MockMVC MySQL netbeans repository REST RestTemplateBuilder scm Security SOAP software development spanners spring Spring-WS spring boot spring mvc spring security tapestry test testing tomcat unit test VM windows WithMockUser