3 Integration Continuous Integration Guide
4 ----------------------------------------
7 Continuous Integration is key due to the complexity of the ONAP projects.
8 Several chains have been created:
12 - Gating: On demand deployment of a full ONAP solution to validate patchsets
14 They are run on different environments (Orange labs, DT labs, Azure Cloud).
16 The following document will detail these chains and how you could set up such
17 chains and/or provide test results to the community.
19 Integration CI Ecosystem
20 ------------------------
25 The global ecosystem can de described as follows:
27 .. figure:: files/CI/ONAP_CI_10.png
30 Several chains are run in ONAP.
31 The CI chains are triggered from different CI systems (Jenkins or gitlab-ci) (1)
32 on different target environments hosted on community labs (Windriver,
33 Orange, DT, E///) or Azure clouds. Jobs (installation, tests) are executed on
34 these labs (2). At the end, the results are pushed through the OPNFV test API (3)
35 to a test database (4) hosted by Linux Foundation on
36 http://testresults.opnfv.org.
37 Results can be reported in different web pages hosted on LF or on gitlab.com (5).
43 CI daily chains (Master and last Stable) are run on Orange, DT using gitlab-ci
44 jobs and Ericsson using jenkins jobs.
49 OOM gating has been introduced for El Alto. It consists of a deployment followed
50 by a set of tests on patchsets submitted to OOM repository.
52 The CI part is managed on gitlab.com and the deployment is executed on ONAP
53 Orange lab and Azure clouds.
54 The goal is to provide a feedback - and ultimately to vote - on code change
55 prior to merge to consolidate the OOM Master branch.
57 The developer can evaluate the consequences of his/her patchset on a fresh
60 The gating is triggered in 2 scenarios:
63 - comment with the magic word **oom_redeploy** is posted in the Gerrit's comment
66 The procedure to submit new feature in CI is done in 3 steps as described in the
69 .. figure:: files/CI/ONAP_CI_0.png
73 Visualization of the CI pipelines
74 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
76 As the CI chains are triggered from different systems, several web interfaces
77 can be used to visualize them.
79 A web site has been created to centralize the links on http://testresults.opnfv.org/onap-integration/index.html
81 For Gating and gitlab.com based CI chains, the pipelines consist in pipelines of
82 pipelines managed through the chaining of .gitlab-ci.yml file thanks to an Open
83 Source deployment called chained-ci (https://gitlab.com/Orange-OpenSource/lfn/ci_cd/chained-ci).
84 A visualization tool is available to list all your chains as described in the
87 .. figure:: files/CI/ONAP_CI_1.png
91 If you click on any element of the chain, you will open a new window:
93 .. figure:: files/CI/ONAP_CI_2.png
96 In order to provide the logs to the developer an additional web page has been
97 created to summarize the tests and grant access to their associated logs:
99 .. figure:: files/CI/ONAP_CI_8.png
103 Additionnaly, for the daily chain, another page displays the results as time
104 series, allowing to see the evolution of the tests over time.
106 .. figure:: files/CI/ONAP_CI_9.png
111 Setup Your Own CI Chains
112 ------------------------
114 If you want to setup a gitlab.com based CI chain, and want to use chained-ci,
115 you can follow the tutorial on https://gitlab.com/Orange-OpenSource/lfn/ci_cd/chained-ci-handson
117 You should be able to chain your automation projects:
120 * Deployment of Kubernetes
121 * Test of your Kubernetes (using OPNFV functest-k8s tests)
122 * Deployment of your ONAP (you can use your own automatic installation
123 procedure or https://gitlab.com/Orange-OpenSource/lfn/onap/onap_oom_automatic_installation/)
124 * Test ONAP thanks to the differnet ONAP xtesting dockers covering infrastructure
125 healthcheck, components healthcheck tests, end to end tests, security tests.
127 If you want to report your results to the community, do not hesitate to contact
128 the integration team. The Test database is public but the pods must be declared
129 to be allowed to report results from third party labs.