Setup Auto SSH Login

SSH to Jenkins Master
    $ sudo -iu jenkins
Generate Public & Private RSA Key.
    $ ssh-keygen -t rsa
       public key location : /var/lib/jenkins/.ssh/id_rsa.pub
       private key location : /var/lib/jenkins/.ssh/id_rsa
Create .ssh directory on Jenkins Slave 1 from Jenkins Master
    $ ssh -i /home/ubuntu/bin/myaccountkey.pem ubuntu@3.91.65.12 mkdir -p .ssh
Attach master public key with slave authorized directory
    $ cat .ssh/id_rsa.pub | ssh -i /home/ubuntu/bin/myaccountkey.pem ubuntu@3.91.65.12 'cat >> .ssh/authorized_keys'
Verify connection
    $ ssh ubuntu@3.91.65.12
Create .ssh directory on Jenkins Slave 2 from Jenkins Master
    $ ssh -i /home/ubuntu/bin/myaccountkey.pem ubuntu@3.95.20.115 mkdir -p .ssh
Attach master public key with slave authorized directory
    $ cat .ssh/id_rsa.pub | ssh -i /home/ubuntu/bin/myaccountkey.pem ubuntu@3.95.20.115 'cat >> .ssh/authorized_keys'

Download Jenkins Slave 1 Agent Program on Jenkins Slave 1 Machine

SSH to Jenkins Slave 1
Create bin directory.
    $ mkdir ~/bin
Goto bin and download slave.jar from master
    $ cd bin 
    $ wget http://54.81.205.161:8080/jnlpJars/slave.jar

Add Jenkins Slave 1 Machine to Jenkins Master
Login to Jenkins site

Launch Command
    $ ssh ubuntu@3.91.65.12 java -jar ./bin/slave.jar

Download Jenkins Slave 2 Agent Program on Jenkins Slave 2 Machine

SSH to Jenkins Slave 2
Create bin directory.
    $ mkdir ~/bin
Goto bin and download slave.jar from master
    $ cd bin 
    $ wget http://54.81.205.161:8080/jnlpJars/slave.jar

Add Jenkins Slave 2 Machine to Jenkins Master
Login to Jenkins site

Launch Command
    $ ssh ubuntu@3.95.20.115 java -jar ./bin/slave.jar

tomcat/conf/server.xml, controls tomcat server-level stuff, like ports
tomcat/conf/tomcat-users.xml, edit to insert users for tomcat manager app
tomcat/webapps/_webappname_/WEB-INF/web.xml, webapp-internal configs for a specific webapp
tomcat/conf/Catalina/localhost/_webappname_.xml, server-level configs for a specific webapp auto-created when tomcat is started
tomcat/conf/context.xml, default values for server-level webapp configs, seldom changed, overridden by webapp-specific context xml file
tomcat/conf/web.xml, default values for webapp configs, seldom changed, overridden by webapp-specific web.xml file
tomcat/conf/logging.properties, controls tomcat logging details, seldom changed
tomcat/conf/catalina.properties, tomcat internal classloader configs, don't mess with it.
tomcat/conf/catalina.policy, tomcat internal security policy, don't mess with it.

Explanation:

Following are the levels of variable precedence arranged from the least (always gets overridden) to the most (can override anything below it):
1. Role defaults
2. Inventory files (host_vars > group_vars > vars)
3. Playbook group_vars
4. Playbook host_vars
5. Host facts
6. Variables files > vars_prompt > vars
7. Variables created using the register clause
8. Variables files created inside Roles and those set by the include_vars module
9. Variables defined in a block
10. Variables defined in a task block
11. Any variables passed through -e during command execution

Explanation:

Command to view the execution status

$ echo $?

Exit status output will be 0,1 or 2 where 0 --> Success, 1 --> Minor problems and 2 --> Serious problem

Docker-CheatSheet.pdf (548.16 kb)