Java Magazine, Mar/Apr 2018
DevOps with Container Based Delivery Pipelines A real world pipeline for automating delivery of a containerized Java EE app to the cloud with a Jenkins based toolchain ORACLE COM JAVAMAGAZINE MARCH APRIL 2018 32 microservices and containers In this article I examine how to implement DevOps using the widely used Jenkins tool Docker containers and a cloud hosted instance of Java EE DevOps is a term invented in 2009 to emphasize the cooperation of developers and operations personnel in building and deploying applications DevOps is often focused on shortening cycle time that is making it easier to push out new product releases quickly How does DevOps relate to other disciplines Continuous delivery is the capability to make changes to a product available frequently whereas continuous deployment refers to the process of effectively bringing those changes to the end user Continuous inspection and continuous integration are building blocks of continuous delivery Continuous inspection emphasizes that high quality is always mandatory Continuous integration is the practice of checking in changes to a version control system several times a day and ensuring that the code in version control can be checked out anytime and builds successfully Continuous delivery is the prerequisite for continuous deployment and in turn DevOps is the prerequisite for continuous delivery The Basic Use Case Because my colleagues and I do not want to reinvent the wheel we try to share good practices and synergies on toolchains So centralized tools above all the automation engine Jenkins are the foundation of our DevOps initiative This means that from the moment we push a change to our version control system in our case Git the overall process of testing packaging containerization staging and promotion MICHAEL HÜTTERMANN
You must have JavaScript enabled to view digital editions.
