Jenkins is an extensible open source continuous integration server. See the details from here.

Linux Foundation provides Jenkins for OPNFV. You can access it from this link.

The method that is normally used for connecting servers(slaves) to Jenkins requires SSH access to servers from outside. This may not be something to fix quickly for all the labs so we use the alternative way to connect slaves to Jenkins.

This alternative uses JNLP. Via JNLP, slaves open connection towards Jenkins instead of Jenkins accessing to them.

The server you want to connect to OPNFV Jenkins must have access to internet obviously.

Please follow below steps to enable this.

• Please create a ticket by sending mail to OPNFV LF Helpdesk first, opnfv-helpdesk@rt.linuxfoundation.org.
• 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. (user could be named jenkins for example)
• Download slave.jar to server you want to connect to OPNFV Jenkins using this link: https://build.opnfv.org/ci/jnlpJars/slave.jar
• Create a directory /home/jenkins/opnfv_slave_root
• Ping/contact LF(Aric) via chat as getting the server connected requires Aric's help.
• Ask Aric to create a slave on OPNFV Jenkins. The slave should use JNLP as method. (You can mention Ericsson slave so he can copy that slave and do small modifications on it.)
• Provide needed information to Aric such as the IP of the server, name for your slave, slave root ( /home/jenkins/opnfv_slave_root for example) and so on.
• Aric should provide you the key/token you need to use.
• Have a quick 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_you_get_from_Aric>
• Navigate to OPNFV Jenkins and look for your slave. It should have some executors in "Idle" state if the connection is successful. (https://build.opnfv.org/ci/)
• Aric will probably create a "HelloWorld" job and execute it on the slave to verify basic functionality.
• Once you reach this step, you have the server connection to OPNFV Jenkins completed. You can script the command you used above so the connection between slave and Jenkins can be kept open.

The slaves connected to OPNFV Jenkins using the method explained above are listed below.

https://build.opnfv.org/ci/computer/

The ones that don't have red cross next to computer icon are fully functional.

Certain things need to be set up in order to use Jenkins in CI. Below list contains some of the obvious ones.

This is used for connecting slaves to Jenkins. Whatever account is used for connecting slave(s) then used for executing jobs/build.

This account can also be used for running verification jobs on Git commits and giving +1/-1 if certain commit fails passing certain checks such as commit message format, PEP8, and so on. (Account name could be octopus.)

This defines who can do what and which credential is valid for which domain and so on.

These are the servers where the jobs/builds are executed.

These are the jobs that build software, test it and so on. See notes on Creating/Configuring/Verifying Jenkins Jobs

With plugins new functionality can be added to Jenkins in order to handle SCM stuff, create pipelines, throttle builds, logging/graphing, and so on.

Jenkins has hundreds of different plugins that can be installed in order to extend its functionality. One thing to keep in mind is installing huge number of plugins increases the load on the Jenkins master.

Full list of plugins can be seen from this link.

• Connecting slaves to Jenkins with SSH: SSH Slaves Plugin

• Use Git as SCM: Git Plugin
• Integrate Gerrit with Jenkins: Gerrit Plugin
• Integrate Gerrit with Jenkins to trigger jobs: Gerrit Trigger Plugin

• Create jobs that can trigger other jobs and take action depending on result: Parameterized Trigger Plugin
• Create complex/hierarchical jobs: Multijob Plugin
• Create jobs programmatically: Job DSL Plugin
• Create workflows: Workflow Plugin
• Throttle concurrent builds: Throttle Concurrent Builds Plugin

• Integrate Jenkins with Artifactory: Artifactory Plugin

• Send customized emails: Email-ext Plugin
• Make Jenkins talk: Instant Messaging Plugin, Jabber Plugin
• Show quick build status: eXtreme Feedback Plugin
• Create and visualize pipelines: Build Pipeline Plugin
• Use Green Balls for successful builds: Green Balls

An easy option to get started with graphing performance and event logs from test runs is to just use Jenkins with some plugins.

The advantage to having Jenkins do this is the data is readily available for each job. As the number of jobs increased and mining, trends, and more sophisticated numerical data analysis and logging investigation is required the data can also be pushed to external databases such as splunk and logstash.

This plugin provides generic plotting (or graphing) capabilities in Jenkins.

This plugin will plot one or more single values variations across builds in one or more plots. Plots for a particular job (or project) are configured in the job configuration screen, where each field has additional help information. Each plot can have one or more lines (called data series). After each build completes the plots' data series latest values are pulled from Java properties file(s), CSV file(s), or XML file(s) via an XPath (which you should have generated during the build) somewhere below you workspace. Data for each plot is stored in a CSV file within the job's root project directory.

It can generate various kind of plots, including Area, Bar, Line, Stacked Bar, Waterfall…

Here is an example of the plots generated by this plugin:

See more details here: https://wiki.jenkins-ci.org/display/JENKINS/Plot+Plugin