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 (Jenkins -> Configuring Jenkins Jobs).
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 OPEN-O ONAP project is expected to setup their project to inherit from the ONAP ci-management artifacts.
| Info | ||
|---|---|---|
| ||
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.
| Code Block | ||||
|---|---|---|---|---|
| ||||
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 VNF-SDK into Jenkins, by editing ci-management /jjb/vnf-sdk-design-pkg/vnf-sdk-design-pkg.yaml file.
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 mailing list or the helpdesk by using this email address helpdesk@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