Distributed Jenkins

Notes on the Jenkins Deployment for Scalability around Pull Requests from GitHub.

Close to: http://devopscube.com/setup-slaves-on-jenkins-2/

1. on master:

Generate an id_rsa key, for example:

 ssh-keygen -t rsa -C "The access key for Jenkins slaves" 

make sure the chmod's are right copy the public key

Important: This is all based on the key under /var/lib/jenkins/.ssh/ being with the following owner and access permissions:

  -rw-------.  1 jenkins jenkins 1675 Dec 21 21:20 id_rsa
  -rw-r--r--.  1 jenkins jenkins  419 Dec 21 21:20 id_rsa.pub

(see credentials below based on file)

1. on slave

Make sure the following are installed with the correct version of Java for the given release:

• Java
• git
• Globalyzer Lite under ~jenkins/lingoport/globalyzer-lite-x.y
• .globalyzerrc
• sonar-scanner under jenkins/lingoport/sonar-scanner-x.y/
  • the configuration file must point back to the Dashboard Server!

copy the public key (id_rsa.pub) into

.ssh/authorized_keys

make sure the chmod is 600, as in:

-rw-------. 1 jenkins jenkins  831 Dec 21 23:05 authorized_keys

Note: Make sure in the copy you have one line for the copy. Sometimes, copying may break the key into multiple lines.

1. In AWS console / the master and slave nodes:

 Open the 22 ports to and from the two systems. 

1. On slave:

1. On Master:

When click OK. The Node should go on-line. The top of the log should look like:

 [12/22/16 15:47:13] [SSH] Opening SSH connection to 54.89.231.113:22.
 [12/22/16 15:47:13] [SSH] Authentication successful.
 [12/22/16 15:47:13] [SSH] The remote users environment is:
 

On your master machine go to Manage Jenkins > Manage Nodes.