Lets say we have two Jenkins server namely JenkinsOne and JenkinsTwo and we have a job name “TEST” on JenkinsTwo which we want to trigger from JenkinsOne.<\/p>\n
To achieve the above stated task, we need to download Parameterized Remote Trigger Plugin on JenkinsOne. You can do that by clicking on Manage Jenkins option and then choosing Manage Plugins, wherein you can search and download the desired plugin.<\/p>\n
Our JenkinsTwo server has password based access. So to trigger a job on it, first we need to log in to the server and then build the job. For this to happen from a remote server, we need to provide credentials to it. So before triggering a remote build on JenkinsOne, set the credentials by following the below mentioned steps.<\/p>\n
Step 1:<\/strong> Step 2:<\/strong> Step 3:<\/strong> Specify scope, username and password and save the changes.<\/p>\n Step 4:<\/strong> Step 5:<\/strong> Step 6:<\/strong> Step 7:<\/strong> Step 8:<\/strong> Step 9:<\/strong> Step 10:<\/strong> Step 11:<\/strong> Step 12:<\/strong> At times you encounter a use case where you need to run a Jenkins job remotely from another Jenkins instance. Well, there is a way to achieve this by using Parameterized Remote Trigger plugin. Let’s see how we can\u00a0trigger parameterized or non-parameterized jobs on remote Jenkins server from another Jenkins server. Demonstration Lets say we […]<\/p>\n","protected":false},"author":204,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":95},"categories":[1174,1],"tags":[1682,1934,1930,1931],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/21823"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/204"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=21823"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/21823\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=21823"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=21823"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=21823"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nGo to Manage Credentials option after choosing Manage Jenkins option on your console.<\/span><\/span><\/p>\n![\"2\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/23.png\")
<\/p>\n
\nAfter that, choose add domain option. As our JenkinsTwo is a remote server so we need to specify its host name here.<\/span><\/span><\/p>\n![\"3\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/33.png\")
<\/p>\n
\nAfter this\u00a0specify the credentials so that we can log into JenkinsTwo. Since on the JenkinsTwo server we have password based authentication, we have to choose “Username with password” option as shown in the screenshot below.<\/span><\/span><\/p>\n![\"4\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/43.png\")
<\/p>\n![\"5\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/52.png\")
<\/p>\n![\"6\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/62.png\")
<\/p>\n
\nNow go to Configure System option after selecting Manage Jenkins option. \u00a0Under Parameterized Remote Trigger Configuration, click on Add.<\/span><\/span><\/p>\n![\"8\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/83.png\")
<\/p>\n
\nAs soon as we click on Add, the Display name field will automatically show\u00a0already added remote Jenkins server which is JenkinsTwo. After checking the “Use the credentials Plugin” option, we can see the already provided credentials. Now to access the server, we need to provide JenkinsTwo\u00a0address and port number.<\/span><\/span><\/p>\n![\"9\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/93.png\")
<\/p>\n
\nNow make a new job in JenkinsOne. Here we are making this as a parameterized job, since our “TEST” job on JenkinsTwo is parameterized.<\/span><\/span><\/p>\n![\"10\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/104.png\")
<\/p>\n
\nNow under the Build section, choose “Trigger a remotely parameterized job” option in the drop down menu of “Add build step” option as shown below.<\/span><\/span><\/p>\n![\"11\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/113.png\")
<\/p>\n
\nAfter doing that, we can choose our remote Jenkins server in “Select a remote host” field.<\/span><\/span><\/p>\n![\"12\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/121.png\")
<\/p>\n
\nType the name of the job which you want to build on remote jenkins server i.e. “TEST” job on JenkinsTwo server in our case. Specify the parameter i.e “NAME” required by the “TEST” job. Also, we need to use the value defined here in “name” parameter as shown below. Save your configuration changes.<\/span><\/span><\/p>\n![\"13\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/132.png\")
<\/p>\n
\nThe final step remaining is to Build the job.<\/span><\/span><\/p>\n![\"14\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/141.png\")
<\/p>\n
\nAfter building the job, in the Console Output we can see that the job has been remotely built if all the configuration changes have been made correctly.<\/span><\/span><\/p>\n![\"15\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/151.png\")
<\/p>\n
\nOn our remote server \u00a0“JenkinsTwo”, if we can log in, we can verify that our job has been executed with the parameter’s value that was provided on JenkinsOne server and by the same user whose credentials we provided in the \u00a0initial steps.<\/span><\/span><\/p>\n![\"16\"](\"\/blog\/wp-ttn-blog\/uploads\/2015\/06\/16.png\")
<\/p>\n","protected":false},"excerpt":{"rendered":"