Deploying and configuring Jenkins
Jenkins originally started life as an open source build server, originally called Hudson (the name was changed followinga dispute with Oracle), whose sole purpose was to compile Java applications. Since it was first released in 2004, its role has been greatly expanded and it is now considered to be one of the leading continuous integration and continuous delivery solutions available and not just a build server for Java applications.
Before we can deploy our test application, we need to deploy and configure Jenkins. The following are the steps you need to take to get a full Jenkins server deployed and configured.
Deploying the Jenkins container
Before we launch and configure our Jenkins container in our Docker Swarm cluster, we need to create an image. For this, we will be using the official Jenkins image as a base and then we will add a few of our own customizations:
- We will start by preparing a Jenkins configuration file; the file should be named
init.groovy...