...
- How long the project has been an active: This repo has been active since launch and as recent as 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 |
| Cassablanca ( 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 ) | 272 | 71 | 11 |
| Frankfurt ( 10/25/2019 to 6/18/2020 ) | 482 | 79 | 11 |
Architecture Alignment:
- N/A
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.