Gitiles
Code Review Sign In
gerrit.nordix.org / oransc / ci-management / 8a4f190afa328ea560c1e391362b6f2f974e0019
commit8a4f190afa328ea560c1e391362b6f2f974e0019[log] [tgz]
authorAndrew Grimberg <agrimberg@linuxfoundation.org>Wed Jun 12 09:33:54 2019 -0700
committerAndrew Grimberg <agrimberg@linuxfoundation.org>Wed Jun 12 09:33:54 2019 -0700
tree89f2e1dd01f8cc6d3866089a6ca2a0d4b9cc321b
parentdb2347d5cb9f13ede8223c9001149e0338710f43 [diff]
Fix yaml linting issues

My local tox tests are throwing several yamllint problems that are not
being picked up by the CI system. Likely due to a slightly older version
of yamllint in the CI.

Change-Id: Ie704b98228af626e0a22aa936ebbb445e3a8d5d1
Signed-off-by: Andrew Grimberg <agrimberg@linuxfoundation.org>
10 files changed
tree: 89f2e1dd01f8cc6d3866089a6ca2a0d4b9cc321b
  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.

Custom JJB templates for Docker Java projects

Custom JJB templates are defined for projects that use Maven to compile Java code and build a Docker image. These projects should use the following jobs in the project.yaml file::

jobs:
  - gerrit-maven-docker-verify
  - gerrit-maven-docker-merge
  - gerrit-maven-docker-stage

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.