Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

Overview

Jobs in ONAP are not configured through the Jenkins UI, but rather through Jenkins Job Builder. That helps to have all the configuration of the projects under Source Control (48534203).

Jenkins UI can be used to monitor the Jobs status and access the log files.

To understand how to create and configure Jenkins job, look at what has been documented for OpenDayLight at Jenkins.

Every ONAP project is expected to setup their project to inherit from the ONAP ci-management artifacts.

Official RelEng Jenkins documentation

Official RelEng docs with more information:

Jenkins → https://docs.releng.linuxfoundation.org/en/latest/jenkins.html

Jenkins Sandbox → https://docs.releng.linuxfoundation.org/en/latest/jenkins-sandbox.html

Get your project visible into Jenkins

To get your jobs to appear in the ONAP Jenkins-master silo, create a <project>.yaml file in the ci-management project’s jjb directory.

Java project should use this yaml template to setup their Jenkins job.

Python project should use this yaml template to setup their Jenkins job.

Create JJB Directory
git clone https://gerrit.onap.org/r/ci-management
cd ci-management
mkdir jjb/<new-project>
....
Then edit jjb/<project>/<project>.yaml file
Commit your changes into Gerrit


Example:

This is a very simple example to create an entry for ci-management in the corresponding project yaml file:

https://github.com/onap/ci-management/blob/master/jjb/ci-management/ci-management.yaml#L8


If you have any questions on how to configure <project>.yaml file, email your questions to the onap-discuss@lists.onap.org 



Testing your jobs on the Sandbox

https://jenkins.onap.org/sandbox/

Please look for the instruction in ci-managment/Sandbox_Setup.md to learn how to use the sandbox



  • No labels