Page History

...

1. Create a user named Jenkins on the machine you want to connect to Akraino Jenkins and give the user sudo rights.
2. Install needed software on the machine you want to connect to Akraino Jenkins as an agent.
   1. openjdk 8
   2. monit
3. If the agent will be used for running virtual deployments, Functest, and Yardstick, install below software and make Jenkins user the member of the groups.
   1. docker
   2. libvirt

4.  Create agent root in Jenkins user home directory.

   Code Block
   language bash
   mkdir -p /home/jenkins/akraino/agent_root

   
   

5. Clone Akraino ci-management repository.

   Code Block
   language bash
   mkdir -p /home/jenkins/akraino/repos cd /home/jenkins/akraino/repos git clone https://gerrit.akraino.org/r/ci-management

   
   

6. Add all required information to the Community managed Jenkins agents wiki page.

7. Contact LF by submitting a ticket to the LF Support Desk and request creation of an agent on Akraino Jenkins. Include below information in your mail.

   1. Remote root directory (/home/jenkins/akraino/agent_root)

   2. Number of executors (the number of concurrent jobs to allow on the agent).
   3. Label(s). The label(s) define what jobs can be run on a particular agent. Each job should have a build-node defined in its JJB definition.
   4. An agent name. This has generally followed the convention of "<OS>-dev-<CPUs>c-<RAM>g", though this is not a strict rule. The important thing is that the name is a unique and useful identifier. Other elements, such as "prd" or "snd" to identify the environment or numbering at the end, will be added by LF.
8. You will receive a confirmation from LF containing the complete agent name and a secret token.

9. Run the following script in order to make sure there is no problem connecting. You should see INFO: Connected in the console log.
   

   Code Block
   language bash
   cp /home/jenkins/akraino/repos/ci-management/utils/jenkins-jnlp-connect.sh /home/jenkins/ cd /home/jenkins sudo ./jenkins-jnlp-connect.sh -j /home/jenkins -u jenkins -n <agent name on Akraino Jenkins> -s <the token you received from LF> -t

   
   

   1. If you receive a connectivity error, then you need to check your firewall and allow outgoing connections for the port.

10. Kill the Java agent.jar process.

11. Run the same script normally without test (-t) in order to get monit script created.

    Code Block
    language bash
    sudo ./jenkins-jnlp-connect.sh -j /home/jenkins -u jenkins -n <agent name on Akraino Jenkins> -s <the token you received from LF>

    
    

12. Edit monit configuration and enable http interface. The file to edit is /etc/monit/monitrc on Ubuntu systems. Uncomment below lines.
    

    Code Block
    # set httpd port 2812 and # use address localhost # only accept connection from localhost # allow localhost # allow localhost to connect to the server and

    
    

13. Restart monit service.

    1. Without systemd:
       sudo service monit restart

    2. With systemd: you have to enable monit service first and then restart it.
       sudo systemctl enable monit
sudo systemctl restart monit

14. Check to see if Jenkins comes up as managed service in monit.
    sudo monit status

15. Connect agent to Akraino Jenkins using monit.
    sudo monit start jenkins

16. Check agent on Akraino Jenkins to verify the agent is reported as connected. The agent on Akraino Jenkins should have some executors in “Idle” state if the connection is successful.