You have just seen how much work it is to set up a new Jenkins server. While it is not a Herculean effort, there are at least five steps you have to do before you can pick your plugins and log in to get to work. And in the spirit of the game show Name That Tune, I can deploy a Jenkins server in three steps, and the first two are just to allow our Jenkins data to persist beyond the life of the Docker container that hosts the Jenkins server. Assuming you have a Docker host set up-and-running as per the instructions in Chapter 1, Setting up a Docker Development Environment, we want to create a location for the Jenkins server to store its data. We will create a folder and assign ownership to it. It will look like the following:
# Setup volume location to store Jenkins configuration
mkdir $HOME/jenkins_home
chown 1000 $HOME/jenkins_home
The owner...