Skip to content

omec-project/omec-project-ci

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

OMEC Project CI

This repo contains automation used for testing and continuous integration for OMEC Project repos.

Code review process

OMEC uses Github's Pull Request process coupled the CORD Jenkins which is part of the CORD Project.

If you'd like to make a code contribution:

  1. Clone a copy of (or make a fork of) one of the OMEC-Project repos, make changes using git then submit a Pull Request on the main OMEC repo.

  2. One of the OMEC Project members will review your patchset. If it's approved, a comment with ok to test will be left on the pull request, and a OMEC Jenkins Job will be started to test your patchset.

  3. If the patchset passes tests, it can be merged into the project.

Notes for Code Reviewers

OMEC uses the Jenkins GitHub Pull Request Builder Plugin to handle Pull Request reviews - see that page for the proper comments to leave to retest and perform other interactions between Github and Jenkins.

Developing Jenkinsfiles

Your Jenkinsfiles can be checked with the jflint.sh script, which requires that they use the Declarative Pipeline Syntax.

Please use this script to test your Jenkinsfiles before commit.