Gitiles
Code Review Sign In
gerrit.nordix.org / oransc / ci-management / a70adf26aa0447d9c981c19b27dde3db7e38838e
commita70adf26aa0447d9c981c19b27dde3db7e38838e[log] [tgz]
authorAlex Stancu <alexandru.stancu@highstreet-technologies.com>Fri Nov 06 17:30:41 2020 +0200
committerAlex Stancu <alexandru.stancu@highstreet-technologies.com>Fri Nov 06 17:31:13 2020 +0200
tree3a044e92decdbc84b5e6748946c287657f84a5db
parentb255f0beb3afe9c750221fd12a58906ad4a9d54e [diff]
Refactor build jobs of sim/o1-interface repo.

Issue-ID: SIM-38
Change-Id: I1c4711b82c0c22f51f099b2a7679c5b0dbd764a8
Signed-off-by: Alex Stancu <alexandru.stancu@highstreet-technologies.com>
1 file changed
tree: 3a044e92decdbc84b5e6748946c287657f84a5db
  1. docker/
  2. jenkins-config/
  3. jjb/
  4. packer/
  5. global-jjb
  6. .coafile
  7. .gitignore
  8. .gitmodules
  9. .gitreview
  10. .yamllint.conf
  11. README.md
  12. tox.ini
README.md

Continuous Integration for O-RAN SC at LF

This repo contains configuration files for Jenkins jobs for the O-RAN SC project.

Defaults.yaml

To avoid repetition, many required configuration parameter values are defined in the defaults.yaml file.

Custom JJB templates for Docker CI PackageCloud projects

Custom JJB templates are defined for projects that use Docker to compile code and build DEB/RPM packages, then push the packages to PackageCloud.io. These projects should use the following jobs in their respective project.yaml file::

jobs:
  - gerrit-docker-verify
  - oran-gerrit-docker-ci-pc-merge

Testing the templates

These instructions explain how to test the templates using the Jenkins sandbox. This catches errors before submitting the changes as Gerrit reviews.

Prerequisites

Install the Jenkins job builder:

pip install jenkins-job-builder

Check out the global JJB templates submodule within this repo:

git submodule update --init

Test Locally

Check sanity by running the Jenkins job-builder script in this directory:

jenkins-jobs test -r jjb

Deploy the templates to the Jenkins sandbox

Login (after requesting membership in group oran-jenkins-sandbox-access) at the Jenkins sandbox:

https://jenkins.o-ran-sc.org/sandbox

Get the authentication token from the sandbox: a) click on your user name (top right) b) click Configure (left menu) c) under API Token, click Add new Token (button) d) copy the token string

Create a config file jenkins.ini using the following template and your credentials (user name and API token from above)::

[job_builder]
ignore_cache=True
keep_descriptions=False
recursive=True

[jenkins]
query_plugins_info=False
url=https://jenkins.o-ran-sc.org/sandbox
user=YOUR-USER-NAME
password=YOUR-API-TOKEN

Build and deploy a specific job using the EXACT job name.

jenkins-jobs --conf jenkins.ini update jjb your-job-name-here

Examples:

jenkins-jobs --conf jenkins.ini update jjb project-maven-docker-verify-master-mvn33-openjdk8

In the sandbox visit the job page, then click the button "Build with parameters" in left menu.

How to build from a Gerrit review branch

This explains how to launch a "verify" job in the Sandbox on an open review. Most "verify" jobs accept parameters to build code in a review submitted to Gerrit. You must specify the change ref spec, which is a Git branch name. Get this by inspecting Gerrit's "download" links at the top right. The branch name will be something like this:

refs/changes/78/578/2

The first number is a mystery to me; the second number is the Gerrit change number; the third number is the patch set within the change.

Enter this name for both the GERRIT_BRANCH and the GERRIT_REFSPEC parameters, then click Build.