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 2 Next »

Review Submission Date: Jan 11, 2021

Project Description: 

CI-management repo hosts all configuration for Jenkins Job Builder that generates all Jenkins jobs into jenkins.onap.org. It also hosts all configuration for cloud management

and scripts for CI CD procedures. 

Project Landing Page:  

The documentation behind ci-management is maintained globally by LFRELENG under https://docs.releng.linuxfoundation.org/en/latest/jenkins.html

Project Meeting Minutes:  

Meetings for this project are currently done at internal company level in LF

Leadership Resources :

Role

Name
(must use @ macro )

Linux Foundation Login (LFID)

Email Address 
(if different from @ macro)

PTLJessica Gonzalezjwagantall
CommittersBengt Thuree (Unlicensed)bthuree

Andrew Grimbergagrimberg

Eric Balleball

Morgan Richommemrichomme

bgrzybowski

Lasse Kaihlavirtakaihlavi

Project & Release History

  • How long the project has been an active:  This repo has been active since launch and as recent as 2017-01-24
  • Release Participation:  ci-management uses lftoolsm global-jjb and common-packer releases to stay up to date. This includes:
  • Engagement levels for past releases (up to 3): 
    • Commits per Release:  ci-management on its own does not generate releases, but it reflects releases from lftools, global-jjb and common-packer
    • Contributors per Release: LFRELENG
    • Companies per release: The Linux Foundation and, for the past month (since Dec 2020), Orange and Samsung 
  • Use Cases:  CI-management is responsible for every other repo's CI/CD operations.

Architecture Alignment:

  • N/A

Artifact Information:

  • There are no artifacts produced from the configuration hosted in this repo

Other Information:

  • ci-management is the core of every single ONAP repo's CICD workflow. At the moment, there are no ONAP repos in existence that manages their releases without the use of ONAP's Jenkins system. 



  • No labels