Difference between revisions of "Distributed Jenkins"
Line 1: | Line 1: | ||
Notes on the Jenkins Deployment for Scalability around Pull Requests from GitHub. |
Notes on the Jenkins Deployment for Scalability around Pull Requests from GitHub. |
||
+ | # on master: |
||
+ | Generate a key |
||
+ | make sure the chmod's are right |
||
+ | copy the public key |
||
+ | # on slave |
||
+ | copy the public key into |
||
+ | .ssh/authorized_keys |
||
+ | make sure the chmod is 600, as in: |
||
+ | -rw-------. 1 jenkins jenkins 831 Dec 21 23:05 authorized_keys |
||
+ | |||
+ | # In AWS console: |
||
+ | Open the 22 ports to and from the two systems. |
||
+ | |||
+ | # On Master: |
||
+ | Use the ~/.ssh on file |
||
# On master: |
# On master: |
Revision as of 15:19, 22 December 2016
Notes on the Jenkins Deployment for Scalability around Pull Requests from GitHub.
- on master:
Generate a key make sure the chmod's are right copy the public key
- on slave
copy the public key into .ssh/authorized_keys make sure the chmod is 600, as in: -rw-------. 1 jenkins jenkins 831 Dec 21 23:05 authorized_keys
- In AWS console:
Open the 22 ports to and from the two systems.
- On Master:
Use the ~/.ssh on file
- On master:
sudo -u jenkins -H ssh-keygen
- On slave:
On your master machine go to Manage Jenkins > Manage Nodes.