1 .. This work is licensed under a
2 Creative Commons Attribution 4.0 International License.
5 .. integration_main-doc:
11 Integration team deals with 2 different CI/CD systems.
13 - Jenkins CI/CD, CI managed by LF IT and CD by Integration team
14 - GitLab-CI managed by Integration team
16 Continuous Integration
17 ----------------------
19 The CI part provides the following features:
21 - Repository verification (format of the INFO.yaml)
22 - Patchset verification thanks to json/yaml/python/go/rst/md linters. These Jenkins
23 verification jobs are hosted in the ci-management repository. They can vote
24 +1/-1 on patchset submission. Integration team systematically enables linters
26 - Docker build: Integration team builds testsuite dockers and xtesting dockers.
27 These dockers are built then pushed to Nexus through a jjb also hosted in the
28 ci-management repository.
30 The different verification chains are defined in https://jenkins.onap.org/:
32 - CSIT: https://jenkins.onap.org/view/CSIT/
33 - testsuite: https://jenkins.onap.org/view/testsuite/
34 - integration: https://jenkins.onap.org/view/integration/
35 - integration-terragrunt: https://jenkins.onap.org/view/integration-terragrunt/
36 - testsuite-robot-utils: https://jenkins.onap.org/view/testsuite-robot-utils/
38 The Jenkins jobs (jjb) are hosted in https://git.onap.org/ci-management/.
46 This CD is leveraging public gitlab-ci mechanism and used to deploy several ONAP
49 - Daily Master: daily run using OOM Master
50 - Weekly Master: run once a week with longer tests
51 - Gating: run on OOM, clamp or SO patchset submission. It means a full ONAP
52 deployment on demand based on new patchset declared in gerrit.
54 See :ref:`Integration CI guideline <integration-ci>` for details.