aboutsummaryrefslogtreecommitdiffstats
path: root/docs/integration-CICD.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/integration-CICD.rst')
-rw-r--r--docs/integration-CICD.rst19
1 files changed, 10 insertions, 9 deletions
diff --git a/docs/integration-CICD.rst b/docs/integration-CICD.rst
index f7d9f0790..f55bb35ef 100644
--- a/docs/integration-CICD.rst
+++ b/docs/integration-CICD.rst
@@ -10,16 +10,16 @@ CI/CD
.. important::
Integration team deals with 2 different CI/CD systems.
- - jenkins CI/CD, CI managed by LF IT and CD by Integration team
- - gitlab-ci managed by Integration and OOM team
+ - Jenkins CI/CD, CI managed by LF IT and CD by Integration team
+ - GitLab-ci managed by Integration and OOM team
Continuous Integration
----------------------
The CI part provides the following features:
-- Repository Verification (format of the INFO.yaml)
-- Patchset verification thank to json/yaml/python/go/rst/md linters. These Jenkins
+- Repository verification (format of the INFO.yaml)
+- Patchset verification thanks to json/yaml/python/go/rst/md linters. These Jenkins
verification jobs are hosted in the ci-management repository. They can vote
+1/-1 on patchset submission. Integration team systematically enables linters
on any new repository
@@ -35,7 +35,7 @@ The different verification chains are defined in https://jenkins.onap.org/:
- integration-terragrunt: https://jenkins.onap.org/view/integration-terragrunt/
- testsuite-robot-utils: https://jenkins.onap.org/view/testsuite-robot-utils/
-The jenkins jobs (jjb) are hosted in https://git.onap.org/ci-management/.
+The Jenkins jobs (jjb) are hosted in https://git.onap.org/ci-management/.
Continuous Deployment
---------------------
@@ -60,21 +60,22 @@ The Jenkins interface was however used to launch the installation of SB-00.
This Jenkins script is leveraging resources available in OOM and integration
repositories.
-The replacement of this CD by a gitlab runner based CD to unify the CD
+The replacement of this CD by a GitLab runner based CD to unify the CD
management was planned, but finalizing the operation in Guilin was not possible
due to performance issues.
-Gitlab CD
+GitLab CD
.........
This CD is leveraging public gitlab-ci mechanism and used to deploy several ONAP
labs:
- Daily Master: daily run using OOM Master
-- Daily Frankfurt: daily run using the last stable version during Guilin Release
+- Daily Guilin: daily run using the last stable version during Honolulu Release
processing
-- Daily Guilin: daily run setup at RC0 (candidate dockers available for integration)
+- Daily Honolulu: daily run setup at RC0 (candidate dockers available for integration)
- Weekly Master: run once a week with longer tests
+- Weekly Honolulu: run once a week with longer tests
- Gating: run on OOM, clamp or SO patchset submission. It means a full ONAP
deployment on demand based on new patchset declared in gerrit.