Continuous Delivery with Java and Docker: The Good, the Bad, and the Ugly
Implementing a continuous delivery (CD) pipeline is not trivial, and the introduction of container technology to the development stack can introduce additional challenges and requirements. In this talk we will look at the high-level steps that are essential for creating an effective pipeline for creating and deploying containerized applications.
Slides can be found here on slideshare.
Topic covered include:
- The impact of containers on continuous delivery with Java
- The importance of adding metadata to container images
- Validating NFR changes imposed by executing Java applications within a container
- Lessons learned the hard way (in production)
A supporting O’Reilly report “Containerizing Continuous Delivery in Java” will also be available, and this contains instructions and code for how to create a Jenkins-based continuous delivery pipeline that takes a series of Java applications and containerizes them, ready for functional and nonfunctional testing, and ultimately, deployment.
Speaker: Daniel Bryant
Daniel Bryant is the Chief Scientist at OpenCredo and CTO at SpectoLabs. He currently specialises in enabling agility within organisations by introducing better requirement gathering and planning techniques, focusing on the relevance of architecture within agile development, and facilitating continuous delivery. Daniel’s current technical expertise focuses on ‘DevOps’ tooling, cloud/container platforms, and microservice implementations. He also contributes to several open source projects, writes for InfoQ, O’Reilly, and Voxxed, and regularly presents at international conferences such as OSCON, QCon and JavaOne. Find him on twitter @danielbryant.