In this blogpost, we will show you how to provision a Jenkins VM and setup a CI/CD pipeline to connect a code repository in Apache Subversion (SVN) and deploy the application into a Tomcat service.
We start from the solution template in Azure Marketplace, since that’s the fastest and easiest path to get Jenkins up and running in Azure. You can follow the steps using your existing Jenkins server, regardless of whether it’s run on premise or in the cloud. Azure offers Azure Web App with Tomcat on Linux. It is in public preview with build-in support for Tomcat and OpenJDK. It is fully managed by Microsoft and easy to scale. We will demo how to deploy the generated war package into Azure Web App for Java. And of course if you have your own Tomcat server, we will cover this as well.
This is the flow implemented in this post:
- Developers commit code change into Subversion
- Jenkins builds and packages application into war package
- Jenkins deploys the war package into Tomcat service
In the Azure portal, select Create a resource and search for Jenkins. Select the Jenkins offering with a publisher of Microsoft and select Create.
Enter the following information on the basics form and click OK when done.
- Name – name for the Jenkins deployment.
- User name – this user name is used as the admin user for the Jenkins virtual machine.
- Authentication type – SSH public key is recommended. If selected, copy in an SSH public key to be used when logging into the Jenkins virtual machine.
- Subscription – select an Azure subscription.
- Resource group – create a new or select an existing resource group.
- Location – select a location for the Jenkins server.
On the additional settings form, complete the following items:
- Size – Select the appropriate sizing option for your Jenkins virtual machine.
- VM disk type – Specify either HDD (hard-disk drive) or SSD (solid-state drive) for the Jenkins server.
- Virtual network – (Optional) Select Virtual network to modify the default settings.
- Subnets – Select Subnets, verify the information, and select OK.
- Public IP address – Selecting the Public IP address allows you to give it a custom name, configure SKU, and assignment method.
- Domain name label – Specify a value to create a fully qualified URL to the Jenkins virtual machine.
- Jenkins release type – Select the desired release type from the options: LTS, Weekly build, or Azure Verified.
For Integration Settings, select No to use Jenkins host to build the jobs.
In the Azure portal, browse to the Jenkins Resource Group, select the Jenkins virtual machine, and take note of the DNS name.
Browser to the DNS name of the Jenkins VM and copy the returned SSH string.
Open up a terminal session on your development system, and paste in the SSH string from the last step. Update ‘username’ to the username specified when deploying the Jenkins server.
Once connected, run the following command to retrieve the initial admin password.
sudo cat /var/lib/jenkins/secrets/initialAdminPassword
Leave the SSH session and tunnel running, and navigate to http://localhost:8080 in a browser. Paste the initial admin password into the field as seen in the following image. Select Continue when done.
Select Install suggested plugins to install all recommended Jenkins plugins.
Create a new admin user account. This account is used for logging into and working with your Jenkins instance.
Select Save and Finish when done, and then Start using Jenkins to complete the configuration.
Select Manage Jenkins then Manage Plugins. In Available tab, search Maven Integration and Deploy to container and install them.
Jenkins is now configured and ready to build and deploy code. For this example, a simple Java application is used to demonstrate a Jenkins build. It can be found at https://github.com/xiangyan99/java-sample.
Now create a Jenkins build job. Select New Item, give the build project a name such as svn-tomcat-demo, select Maven project, and click OK.
Under source code management, select Subversion and enter your SVN repository URL and credential.
Please download the sample code and check the code into your SVN server.
Under Build, input package for Goals and options.
- Deploy to Azure Web App
Microsoft has a Jenkins plugin to deploy to Azure Web App service.
Under Post-build Actions, select add post-build action and select Publish an Azure Web App. Add your Azure service principal and from the drop-down list, you can choose your Web App Service.
- Deploy to Tomcat server on VM
If you have your own Tomcat server, you can deploy your package to your server as well.
Under Post-build Actions, select add post-build action and select Deploy war/ear to a container. Input Tomcat URL and credential.
To test the build job, manually start a build.
Select Build Now to start a build job. It takes a few seconds for the job to start, when running, you should see status similar to the following images.