Configuration Add-On Appliance
Implementation of the application continuous delivery approach becomes much more simpler and faster with a proper add-on for the automated DevOps pipeline building. Being composed once, it ensures that the majority of Jenkins CI server configurations can be handled automatically, without your interference needed, each time it’s applied. Eventually, you’ll only need to perform some slight tuning according to the specific of a particular project.
So, let’s consider how to quickly integrate the considered CI/CD DevOps approach using the preliminary prepared Jenkins configuration template:
Add-on Installation
1. Navigate to the platform dashboard (for the account your Jenkins environment is running at) and hover over the Tomcat 7 node for the appropriate environment. Click the appeared Add-ons icon to display the same-named tab with the list of suitable pluggable modules:
Locate your add-on (named Jenkins configuration in our case) and Install it with the appropriate button.
2. Wait for the process to be successfully completed and access the Jenkins dashboard (i.e., Open your environment in browser).
As you can see, our continuous integrator already have the list of jobs, that have been prepared automatically.
Jenkins Post-Configurations
To complete the establishment of your Jenkins CI server, a few more slight adjustments should be applied to it:
1. At first, customize the list of jobs with your projects' data:
- specify the link to the repository with your project within the Build and Deploy action
- set the correct credentials inside the Execute shell box for the rest of the jobs
In order to access a particular job’s parameters and change them, use the Configure context menu option (can be called through clicking on the down arrow, which appears upon hovering over the corresponding job):
Tip: In order to be deployed by our sample script (where we use a Git repo with a simple HelloWorld app as an example for this guide), your project should have the proper Maven plugin settings specified within the pom.xml file. You can use this one as a template to adjust your own project’s deployment in the similar way:
- {dev_user}@example.com - login (email address) of the dev user’s account
- {password} - password for the user, specified above
- {cloud_domain} - domain name of your platform
2. The last thing that left to perform is to bind the launching of the first job from our cycle (i.e., Create Environment) to the commit action occurrence at a repository. This can be done through the Webhook option - for example, for a GitHub repo it looks like the following:
That’s all! Now you have a fully configured and ready-to-work integration complex, that waits only for the project change to be committed in order to automatically create an environment, deploy a new application version and move it through the set of required testing and relocation steps. After that, your checked up application will appear at production.
And having the platform attachable add-on for Jenkins configuration already prepared, you can quickly apply this approach to any of your projects through deploying a new continuous delivery mechanism within a few clicks.
