![\"rsz_jenkins\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/12\/rsz_jenkins.jpg\")
<\/p>\nBuilding compressed files of Springboot application is a tedious task and its continuous deployment using Jenkins is even more so. To simplify the above predicament, a new Gradle plugin in Jenkins has been used. So, our objective in this blog \u00a0is to make use of the relation between Gradle and Springboot. Let us take it further.<\/p>\n
Primarily, the GRADLE tool for building a basic Springboot\u00a0application was used using Jenkins as a tool for continuous Integration. Firstly, the GRADLE PLUGIN in Jenkins was added. This was performed using the below flow of steps:<\/p>\n
[shell]Jenkins >> Manage Plugins >> Search for "Gradle" in the "Available" tab.>> Select "Install without restart"[\/shell]<\/p>\n
After the Plugin was successfully installed, a JOB was created and the GIT repository was defined as the SCM. Next, In the Build section the “Invoke Gradle\u00a0Script” option was selected.<\/p>\n
In this section, the various switches, tasks and also the “build.gradle”\u00a0file, in the case of \u00a0a separate build file, were defined.<\/p>\n
By defining a separate “build.gradle”, custom tasks can be added or the output compressed files such as jar or war are customized. A separate build.gradle file is used if one wants to use the same build file for multiple integrations in different Jenkins Jobs. Let’s say we want to overwrite a certain\u00a0parameter in the build file:<\/p>\n
[js]jar {
\n baseName = ‘Mynewapp’
\n version = ‘1.0’
\n}[\/js]<\/p>\n
If it was required to get the output jar file as test-1.0.jar , it could be passed \u00a0as an argument while the gradle\u00a0plugin in Jenkins was invoked.<\/p>\n
<\/p>\n
By the usage of \u00a0the -P switch\u00a0i.e project properties, the parameter that is to be passed can be overwritten in place of the current parameter. Thus, the output jar file as test-1.0.jar was obtained.<\/p>\n
Save the Jenkins job and then build to get the desired results. The build console output was noted as:<\/p>\n
![\"jenk2\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/12\/jenk2.png\")
<\/p>\n
The build resulted in a .jar file as test-1.0.jar that one could run easily using java along with the various JAVA_OPTIONS through the command line.<\/p>\n","protected":false},"excerpt":{"rendered":"
Building compressed files of Springboot application is a tedious task and its continuous deployment using Jenkins is even more so. To simplify the above predicament, a new Gradle plugin in Jenkins has been used. So, our objective in this blog \u00a0is to make use of the relation between Gradle and Springboot. Let us take it […]<\/p>\n","protected":false},"author":178,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":5,"footnotes":""},"categories":[1],"tags":[2878,2877,1511,1682,2072],"class_list":["post-30366","post","type-post","status-publish","format-standard","hentry","category-technology","tag-automate","tag-build-gradle","tag-gradle","tag-jenkins","tag-springboot"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t