The different CI/CD status are distributed accross different platforms depending on what you want to see.
CI
It includes linting, verification, docker built managed by LF IT through Jenkins: https://jenkins.onap.org/
For Integration it includes several items
| Topic | Link | Jobs |
|---|---|---|
| CSIT | https://jenkins.onap.org/view/CSIT/ | Functional tests for the projects |
| Integration | https://jenkins.onap.org/view/integration/ |
|
| testsuite | https://jenkins.onap.org/view/testsuite/ |
|
| oparent | https://jenkins.onap.org/view/ |
...
Integration tests
| oparent/ | maven operation to provide dependency list |
CD
CD is performed in Windriver, Azure and Orange labs
Tests are also executed in other labs (DT, E///) and shared with the community, see http://testresults.opnfv.org/onap-integration/.
...
| Lab | Link | Comments |
|---|---|---|
| Windriver lab |
Deployment triggered by a standalone Jenkins deployed in a Windriver VM (need a VPN access to windriver lab + jenkins credentials shared with Integration committers) |
...
| Azure/Orange | https://orange-opensource.gitlab.io/lfn/ |
...
| ci_cd/chained-ci/ | The CD chains helps to deploy ONAP daily/weekly on OOM/SO/Clamp patchset change. CD is leveraging the chaining of public gitlab-ci CI chains. It is based on public ansible roles shared on gitlab.com (https:// |
...
...
...
) The mechanism is explained in OOM Gating All the results are pushed in a DB and a dahsboard is generated on each run on https://logs.onap.org/onap-integration/ |