...
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
The CI Management project is dedicated to managing the code resources related to the CI systems.
It is intended as a way for the community to collaborate on the design and management of the CI infrastructure where it is possible to do so.and scripts for CI CD procedures.
Project Landing Page:
The documentation behind ci-management is maintained globally by LFRELENG under https://docswiki.releng.linuxfoundationonap.org/en/latest/jenkins.htmlx/X51k
Project Meeting Minutes:
Given the nature of the CI-Management project community meetings are ad-hoc and generally focused on hands-on trouble shooting and corrective
action which does not lend itself well to minute taking. Typically if something of substance needs to be discussed those topics will be in the context of the PTL or TSC meetings.Meetings for this project are currently done at internal company level in LF
Leadership Resources :
Role | Name | Linux Foundation Login (LFID) | Email Address |
|---|---|---|---|
| PTL | Jessica Wagantall | jwagantall | |
| Committers | Bengt Thuree | bthuree | |
| Andrew Grimberg | agrimberg | ||
| Eric Ball | eball | ||
| Morgan Richomme | mrichomme | ||
| bgrzybowski | |||
| kaihlavi |
Project & Release History
- How long the project has been an active: This repo has been active since launch and as recent as launch 2017-01-24
- Release Participation: All ONAP releases.
- Engagement levels for past releases (up to 3):
- Commits per Release: described below
- Contributors per Release: described below
- Companies per release: described below
- Use Cases: CI-management is responsible for every other repo's CI/CD operations.
Statistics taken from https://insights.lfx.linuxfoundation.org/
Release name and timeframe | commits | contributors | companies |
|---|---|---|---|
| Amsterdam ( 1/1/2017 to 11/16/2017 ) | 826 | 74 | 9 |
| Beijing ( 11/17/2017 to 6/7/2018 ) | 433 | 66 | 11 |
| Casablanca ( 6/8/2018 to 11/30/2018 ) | 396 | 71 | 11 |
| Dublin ( 12/1/2018 to 7/9/2019 ) | 424 | 73 | 11 |
| El Alto ( 7/10/2019 to 10/24/2019 ) | 271 | 70 | 11 |
| Frankfurt ( 10/25/2019 to 6/18/2020 ) | 483 | 79 | 11 |
For more detailed contribution per company done in the last 90 day: https://tinyurl.com/yxmsfqoh
Architecture Alignment:
- As a project which supports the ONAP development environment rather than producing ONAP content, architectural alignment of CI-Man components with other ONAP components is not applicable.
Artifact Information:
- ci-management uses lftools, : ci-management uses lftoolsm global-jjb and common-packer releases to stay up to date. This includes:
- https://github.com/lfit/releng-lftools/tags (Releases for lftools)
- https://github.com/lfit/releng-global-jjb/tags (Releases for global-jjb)
- https://github.com/lfit/releng-common-packer/tags (Releases for common-packer)
- )
- 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.