Can Jenkins run work on remote Jenkins

Question

I have 2 Jenkins hosts and would like First Jenkins to run on remote Jenkins based on "SUCCESS" as a result of the first. I looked at various plugins, but all of them seem to point to the ONE JINK host, where several tasks can be linked in this way.

Answer 1

Meanwhile, the available jenkins plugin has appeared, which makes it a lot easier:

https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Remote+Trigger+Plugin

Answer 2

This is very easy to do using cURL queries; there is no need for plug-ins or master> subordinate relationships. It took me 5 minutes from start to start. Use the following guide:

https://www.nczonline.net/blog/2015/10/triggering-jenkins-builds-by-url/

Answer 3

You can configure the work in move 1, which will be built only upon successful completion of the first task on host 1. In this task, you will run the remote assembly, as I described it in this,

Answer 4

Step 1: Install the following plugins in both Jenkins. 1. General Webhook trigger: a job can be started from an http request. 2. HTTP Request Plugin: to send an http request as a build step. 3. Any build step plugin: use any build step in action after build.

Step 2: Configure the job to run (Jenkins B). 1. Select the shared webhook trigger in the assembly trigger and generate a token and paste. 2. After saving, this task can be started by sending an http request to http: // JENKINS_B_URL / generic-webhook-trigger / invoke? Token = TOKEN_VALUE

Step 3: In the main Jenkins (Jenkins A), configure flexible publishing options in the system configuration to allow all build steps to be used as post build actions.

Step 4: In the post-build steps, add another Flexible Publish step. Using this, any assembly action can be used as an action after assembly. Add an HTTP request action. Enter the Jenkins B URL in the URL field and save.

Answer 5

Yes. Configure Jenkins nodes and name them, say master and slave (Manage Jenkins → Manage nodes).

1) Set up Job A and indicate that it can only work on master ("Restrict where this project can be run" and put master in the label field).

2) Configure Job B so that it only works if Job A succeeds:

"Actions after assembly" → "Trigger only if the assembly is successful"

3) Pin Job B to slave as in step 1.