In this guide, we are going to use Docker to configure Jenkins and Tomcat to achieve Continuous Integration/Continuous Deployment. We will install and set up Tomcat and Jenkins using Docker, and thereafter we are going to create a Jenkins Job to deploy your Java application over the Tomcat server. This guide is assuming that you already have basic knowledge of Docker and Docker is up and running on your host machine. So let’s begin with the guide. Jenkins Set up You can spin up a Docker container using the image. Jenkins $ docker container run -dit -p : -v / /run/docker.sock: run/docker.sock -v /data/jenkins/jenkins_home: jenkins_home --name jenkins_container jenkins/jenkins 8080 8080 var /var/ /var/ We are running Jenkins on port . You can see the running container here: 8080 $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ce46107c9f83 jenkins/jenkins:lts "/sbin/tini” Up 1 minutes Up 1 minutes 0.0.0.0:8080->8080/tcp jenkins_container To extract the Jenkins password from Jenkins’s container, you can run below-mentioned command: $ docker exec -it jenkins_container cat / /jenkins_home/secrets/initialAdminPassword gSzHTGfbtXSpcBXMyJ6gzmNfNH7BjhK23 var Copy the admin password from your terminal and open http://your-ip-addr:8080 in your preferred browser. Next, run the initial setup wizard and select . Jenkins will install all the necessary plugins. Recommended Plugins If everything goes well, you will land on the Jenkins’ dashboard area, which looks something like this: Tomcat Set up Now, it’s time to spin the Tomcat container. For this, we are going to use CentOS, which will enable us to set up a customized Tomcat server. You can also use tomcat image as per your choice, however for this guide we are going to stick to the plan. So let's start by pulling the latest Centos image from Docker Hub: $ docker pull centos Using tag: latest latest: Pulling library/centos a29a15cefae: Pull complete Digest: sha256:fe8d824220415eed5477b63addf40fb06c3b049404242b31982106ac204f6700 Status: Downloaded newer image centos:latest docker.io/library/centos:latest default from 8 for To run the container from the pulled image in detached mode, use the command below: $ docker run -dit --name tomcat_container -p : centos 8888 8080 As Jenkins has already occupied port on the machine, here we have opened port for Tomcat in spite the default port being . 8080 8888 8080 To install Tomcat in your Centos container, follow the steps: $ docker exec -it eca291a36127 /bin/bash Go to /opt directory, in your : tomcat_container [root@eca291a36127 /]# cd opt/ Open on your browser. Find “ ” and download the Tomcat binary. At the time of writing this article, the current version is . https://tomcat.apache.org/download-80.cgi Core 8.5.50 [root@eca291a36127 /]# yum install wget [root@eca291a36127 /]# wget http: //apachemirror.wuchna.com/tomcat/tomcat-8/v8.5.50/bin/apache-tomcat-8.5.50.tar.gz Extract the tar file: [root@eca291a36127 /]# tar -xvzf apache-tomcat .tar.gz [root@eca291a36127 /]# cd apache-tomcat /bin/ -8.5 .50 -8.5 .50 Here you are going to find two shell script files named and , assign “execute” permission to both. Both these files allow us to start and stop the Tomcat server, within our container: startup.sh shutdown.sh [root@eca291a36127 bin]# chmod +x shutdown.sh [root@eca291a36127 bin]# chmod +x startup.sh To run the Tomcat server, Java is required. In order to do so, run following command to satisfy the requirement. Here we are going to install OpenJDK 7 using : Yum [root@eca291a36127 /]# yum install java -openjdk-devel -1.7 .0 It’s time to run our Tomcat server; use file to do so: startup.sh [root@eca291a36127 /]# ./startup.sh Using CATALINA_BASE: apache-tomcat Using CATALINA_HOME: apache-tomcat Using CATALINA_TMPDIR: apache-tomcat /temp Using JRE_HOME: opt/apache-tomcat /bin/bootstrap.jar: apache-tomcat /bin/tomcat-juli.jar Tomcat started. /opt/ -8.5 .50 /opt/ -8.5 .50 /opt/ -8.5 .50 /usr Using CLASSPATH: / -8.5 .50 /opt/ -8.5 .50 In your terminal, you can see the message . Now, go to your browser; Tomcat should be accessible at . Tomcat started http://your-ip-addr:8888 In case you want to access the Manage App, you will have to do some additional settings, as by default, the Manager App section can only be accessed from the local system (i.e., ). 127.0.0.1 To overcome this, you will need to make some changes to file. To do so follow the below-mentioned steps: context.xml $ docker exec -it tomcat_container /bin/bash Now, find the file: context.xml $ find / -name context.xml /opt/apache-tomcat /conf/context.xml /opt/apache-tomcat /webapps/host-manager/META-INF/context.xml /opt/apache-tomcat /webapps/manager/META-INF/context.xml -8.5 .50 -8.5 .50 -8.5 .50 Edit the file that resides in webapps directory i.e., , find the Value class name and comment it: /opt/apache-tomcat-8.5.50/webapps/host-manager/META-INF/context.xml org.apache.catalina.valves.RemoteAddrValve ... <!-- --> ... < = = /> Valve className "org.apache.catalina.valves.RemoteAddrValve" allow "127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1" Let's do the same thing on the other file as well, i.e., . /opt/apache-tomcat-8.5.50/webapps/manager/META-INF/context.xml To access the default username and password through the Manager App section, go to and make the following changes: conf/tomcat-users.xml $ /opt/apache-tomcat /conf && nano tomcat-users.xml -8.5 .50 Now, as part of your pipeline, you will have to add a user and define roles on your Tomcat server. To copy the file from the remote machine (in our case, the Jenkins server), you will need to define the role , copy the lines and add it to the end of the file just before the closing tag : Manager Script </tomcat-users> ... <role rolename= /> <role rolename="manager-jmx"/> <role rolename="manager-status"/> <user username="admin" password="admin" roles="manager-gui, manager-script, manager-jmx, manager-status"/> <user username="deployer" password="deployer" roles="manager-script"/> <user username="tomcat" password="s3cret" roles="manager-gui"/> </tomcat-users> ... "manager-gui" < = /> role rolename "manager-script" Since you have made configuration changes in the Tomcat server, you will need to restart the server for the changes to take effect. $ cd /opt/apache-tomcat /bin/ $ ./shutdown.sh $ ./startup.sh Using CATALINA_BASE: apache-tomcat Using CATALINA_HOME: apache-tomcat Using CATALINA_TMPDIR: apache-tomcat /temp Using JRE_HOME: opt/apache-tomcat /bin/bootstrap.jar: apache-tomcat /bin/tomcat-juli.jar Tomcat started. -8.5 .50 /opt/ -8.5 .50 /opt/ -8.5 .50 /opt/ -8.5 .50 /usr Using CLASSPATH: / -8.5 .50 /opt/ -8.5 .50 You can now access the Tomcat Web Application Manager dashboard; username and password are and , respectively. tomcat s3cret Let us move to the next part of the tutorial. Configure Jenkins It’s time to set up Maven and an additional plugin so that Jenkins can connect to Tomcat container over SSH. For this, we are going to install and plugin in Jenkins. Maven Integration Publish over SSH Login to your Jenkins environment and go to , as shown below: Dashboard > Manage Jenkins > Manage Plugins > Available For Maven Integration: For Publish over SSH: Post-installation, you need to configure SSH server details so that Jenkins can connect the Tomcat container. In Jenkins, go to and find . Enter details as shown below: Dashboard > Manage Jenkins > Configure System SSH Servers Test your connection before saving the details. For the sake of this article, we have used the password authentication method, however, it is not recommended in a production environment. We recommend you use a SSH key instead. Deploying WAR file on Tomcat Server using Jenkins As you are through with the configuration part, now you can proceed to create a Jenkins Job. For this simple job, you would need to use . Create a new item, as shown below: Freestyle Project Go to the Source Code Management (also known as SCM), and select . Add your Github or GitLab URL in field: SCM Git Repository URL In the section, select . It periodically polls the VCS to check if any changes were made. During the poll, if any changes were detected in repo since the last build, a new build is initiated. Poll SCM Build Triggers Poll SCM Let's say you want to poll SCM every 30 minutes, then in the text field, add (i.e., every 30 minutes, every hour, every day, every month, and every day of the week). H/30 * * * * Go to section and from the drop-down menu, select , as shown below: Post-Build Step Post-build Actions Send build artifacts over SSH In the field, mention the file name that is going to be uploaded to the server. In case you are not sure about the file name, you can use the pattern as mentioned above . Source files **/*.war Other than this, make sure that you mention the ; in our case, it is . Whereas, for , as you are using Docker for your Tomcat server, use the below-mentioned commands: Remote Directory /root/tomcat Exec command docker cp ~ hello-world.war tomcat_container: apache-tomcat /webapps docker exec -i tomcat_container bash ./opt/apache-tomcat /bin/shutdown.sh docker exec -i tomcat_container bash ./opt/apache-tomcat /bin/startup.sh /tomcat/ /opt/ -8.5 .50 -8.5 .50 -8.5 .50 The above will copy file to your dockerized tomcat container in . Plus, you are making sure that you restart Tomcat to see the changes. hello-world.war /opt/apache-tomcat-8.5.50/webapps Initiate the build process from the Project’s Jenkins Page, and go to the console log output to see if the build was a success or if there is any error/exception. Build Now Your build finished with a SUCCESS message. Now go to your web browser and open . You will see your application index page content. In our case, output is: http://your-ip-addr:8888/hello-world Voila! You have successfully deployed a sample application over Tomcat Server running on Docker with the help of Jenkins Jobs. Now where next? Well it's really up to you. You could possibly try deploying a few more applications running on Docker with Jenkins jobs on your own and let us know your comments. Till then, here are some more Kubernetes and Docker best practices which you might find helpful.
