When you send a package through FedEx it goes through a tracked, automated process that makes sure that the package arrives promptly at the destination. The same should apply to every commit that you check into the trunk. Continuous delivery describes how this process can be made fully automated and transparent and we will show you how your commits can be “fedexed” to production on application servers like JBoss, Tomcat, Weblogic and others with the help from Jenkins and LiveRebel. The main idea of continuous delivery is the deployment pipeline. Every commit that enters the pipeline should go through automated integration and testing and if successful, produce a release candidate. We will show how Jenkins can be used to orchestrate the process all the way to the staging environment. Once we're there, the most complicated phase begins. The release candidate needs to be deployed to production, without disrupting the users or introducing risks. LiveRebel makes production updates quick, automated, non-disruptive and reversible. It finishes the job and delivers the updated version right into the users hands. In this talk we will build a full clustered environment and a deployment pipeline so that commits into the trunk would update a live chat server while you keep on chatting.
15. Questions?
•How do you package the
application?
•Where did it come from?
•Where does it go?
•How does it get deployed?
•What exactly is in prod now?
41. Questions?
•How do you package the
application?
•Where did it come from?
•Where does it go?
•How does it get deployed?
•What exactly is in prod now?
42. Conclusions
•Jenkins jobs represent the
workflow
•Nexus is a sync-point for long-
running workflows
•LiveRebel manages apps and users
•Manual flows with email/REST
•Tracking with scripts & text files
