Description:

You may have already experimented with Docker—running one of the prebuilt images from Docker Hub, for example. If so, you have likely recognized the benefits that Docker, in conjunction with experimentation, offers when building microservices and the advantages the technology brings to development, testing, integration, and, ultimately, production.

But before deploying any containers into a live environment, you must create a comprehensive build pipeline. Integrating containers into a continuous delivery pipeline is far from easy; along with its benefits, Docker presents both technological and process-related challenges. Viktor Farcic gets you started on your Docker journey, addressing Docker's challenges and outlining the steps you need to take to create a fully automated Jenkins pipeline that continuously builds, tests, and deploys microservices into a Docker Swarm cluster.

About Viktor Farcic

Viktor Farcic is a senior consultant at CloudBees. Over the course of his career, Viktor has coded using a plethora of languages including Pascal (yes, he is old), Basic (before it got the Visual prefix), ASP (before it got the .Net suffix), C, C++, Perl, Python, ASP.Net, Visual Basic, C#, JavaScript, Java, Scala, and more. (He never worked with Fortran.) His current favorite is Go. Viktor is passionate about microservices, continuous integration, delivery, and deployment (CI/CD), and test-driven development. He often speaks at community gatherings and conferences. Viktor is the author of The DevOps 2.0 Toolkit: Automating the Continuous Deployment Pipeline with Containerized Microservices and Test-Driven Java Development.