Table of Contents
This document describes how to connect resources (servers) located in Linux Foundation (LF) lab and labs provided by the OPNFV Community to OPNFV Jenkins.
Connecting OPNFV Community Labs to OPNFV Jenkins (c) by Fatih Degirmenci (Ericsson AB)
Connecting OPNFV Labs to OPNFV Jenkins document is licensed under a Creative Commons Attribution 4.0 International License. You should have received a copy of the license along with this. If not, see <http://creativecommons.org/licenses/by/4.0/>.
|2015-05-05||0.1.0||Fatih Degirmenci||First draft|
|2015-09-25||1.0.0||Fatih Degirmenci||Instructions for the Arno SR1 release|
Jenkins is an extensible open source Continuous Integration (CI) server. 
Linux Foundation (LF) hosts and operates OPNFV Jenkins.
Slaves are computers that are set up to build projects for a Jenkins Master. 
Jenkins runs a separate program called "slave agent" on slaves. When slaves are registered to a master, the master starts distributing loads to slaves. 
Term Node is used to refer to all machines that are part of Jenkins grid, slaves and master. 
Two types of slaves are currently connected to OPNFV Jenkins and handling different tasks depending on the purpose of connecting the slave.
The slaves connected to OPNFV Jenkins can be seen using this link: https://build.opnfv.org/ci/computer/ Slaves without red cross next to computer icon are fully functional.
The method that is normally used for connecting slaves to Jenkins requires direct SSH access to servers.  This is the method that is used for connecting slaves hosted in LF Lab.
Connecting slaves using direct SSH access can become a challenge given that OPNFV Project has number of different labs provided by community as mentioned in previous section. All these labs have different security requirements which can increase the effort and the time needed for connecting slaves to Jenkins. In order to reduce the effort and the time needed for connecting slaves and streamline the process, it has been decided to connect slaves using Java Network Launch Protocol (JNLP).
Slaves hosted in LF Lab are handled by LF. All the requests and questions regarding these slaves should be submitted to OPNFV LF Helpdesk.
As noted in corresponding section, slaves from Community Labs are connected using JNLP. Via JNLP, slaves open connection towards Jenkins Master instead of Jenkins Master accessing to them directly.
Servers connecting to OPNFV Jenkins using this method must have access to internet.
Please follow below steps to connect a slave to OPNFV Jenkins.
Create a ticket by sending mail to OPNFV LF Helpdesk first, email@example.com.
Ensure DNS is setup for your public IP addresses: DNS A records and PTR records need to be matching.
Create a local user on server you want to connect to OPNFV Jenkins. (named jenkins for example)
Download slave.jar using https://build.opnfv.org/ci/jnlpJars/slave.jar and place it to somewhere so jenkins user created in previous step can access.
Create a directory /home/jenkins/opnfv_slave_root.
Contact LF by sending mail to firstname.lastname@example.org as getting the server connected requires help from LF.
Slave IP: x.x.x.x
Slave name: company-build
Slave Root: /home/jenkins/opnfv_slave_root
PGP Key: (attached, or exported to key server)
LF will provide you the key/token you need to use.
Try to see if you can establish connection towards OPNFV Jenkins by using below command.
java -jar slave.jar -jnlpUrl https://build.opnfv.org/ci/computer/<slave_name>/slave-agent.jnlp -secret <token>
It is important to keep the slave.jar up to date since OPNFV Jenkins version may be updated any time. In order to make sure you are using compatible version of slave.jar, you can download it from https://build.opnfv.org/ci/jnlpJars/slave.jar whenever you reopen the connection towards OPNFV Jenkins. You may experience random disconnects if you do not do this regularly.
Public PGP Key can be uploaded to public key server so it can be taken from there using your mail address. Example command to upload the key to key server is
gpg --keyserver hkp://keys.gnupg.net:80 --send-keys XXXXXXX
The Public PGP Key can also be attached to the email by storing the key in a file and then attaching it to the email.
gpg --export -a '<your email address>' > pgp.pubkey