Having a continuous deployment pipeline capable of a fully automated application life-cycle is a real sign of maturity of an organization.
This is it. The time has come to put all the knowledge we obtained into good use. We are about to define a "real" continuous deployment pipeline in Jenkins. Our goal is to move every commit through a set of steps until the application is installed (upgraded) and tested in production. We will undoubtedly face some new challenges, but I am confident that we'll manage to overcome them. We already have all the base ingredients, and the main thing left is to put them all together into a continuous deployment pipeline.
Before we move into a practical section, we might want to spend a few moments discussing our goals.