...
Projects with CSIT | CSIT jobs | CSIT job triggers | Tested docker images and repositories | Docker build jobs that create the tested images | Dependencies | Comments | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
aaf | aaf-frankfurt-csit-certservice Frankfurt branch only? The tests triggered from here do not even exist in master (nor are there any jobs for still remaining aafapi and sms-test-plan?) | aaf-certservice-frankfurt-merge-java - this job neither builds a docker image nor triggers another job that does it, so why trigger CSIT? | nexus3.onap.org:10001/onap/ org.onap.aaf.certservice.aaf-certservice-api:frankfurt-latest (hardcoded) The source repository is aaf/certservice | aaf-certservice-maven-docker-stage-frankfurt (note that aaf-certservice-release-verify and aaf-certservice-release-merge also build aaf-certservice-api image, but not with frankfurt-latest tag) | primekey/ejbca-ce:6.15.2.5 (hardcoded, real image used) | How relevant are any of these in Honolulu? | ||||||||||||||||||||||||
appc | appc-master-csit-healthcheck | - | nexus3.onap.org:10001/onap/appc-image:1.7.2-SNAPSHOT-latest nexus3.onap.org:10001/onap/appc-cdt-image:1.7.2-SNAPSHOT-latest (hardcoded) docker-compose.yml as well as appc-image and appc-cdt-image come from appc/deployment | No job is producing these images at the moment! appc-deployment-master-docker-java-daily produces 1.8.0-SNAPSHOT-latest and appc-deployment-frankfurt-docker-java-daily is producing 1.7.3-SNAPSHOT-latest 1.7.2-SNAPSHOT-latest images have not been created since May 27 | mariadb:10.4.3 nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image:0.6.0 (no longer produced, last update to Nexus on Aug 30 2019) nexus3.onap.org:10001/onap/ccsdk-ansible-server-image:0.4.4 (no longer produced, last update to Nexus on Jun 06 2019) (hardcoded, real images used) | Note that APPC is in maintenance mode and its CSIT is to be disabled: https://gerrit.onap.org/r/c/ci-management/+/113561 The tested images are obsolete Frankfurt versions, but the dependencies are even more ancient? Is it any use to update tests to use 1.8.0 if the CCSDK dependencies are not up to date? | ||||||||||||||||||||||||
ccsdk (disabled) | See
| |||||||||||||||||||||||||||||
ccsdk-oran |
The source repository is ccsdk/oran | ccsdk-oran/job/ccsdk-oran-maven-merge-master and ccsdk-oran-maven-merge-guilin produce the tested images respectively (note that these are different images that the STAGING-tagged ones from triggering jobs!) | nexus3.onap.org:10003/onap/sdnc-image (2.1.0-STAGING-latest for master, nexus3.onap.org:10003/onap/sdnc-image:2.0.1-STAGING-latest for Guilin) nexus3.o-ran-sc.org:10004/o-ran-sc/nonrtric-controlpanel:2.0.0 | These tests are currently cloned from ORAN repository and they are essentially plain shell scripts that are just wrapped into Robot In Honolulu the test cases should be brought under ONAP repository and rewritten with Robot and ONAP CSIT scripts as much as possible | ||||||||||||||||||||||||||
clamp | - | nexus3.onap.org:10001/onap/clamp-backend:4.1-STAGING-latest nexus3.onap.org:10001/onap/clamp-backend:4.1-STAGING-latest (hardcoded) The docker-compose.yml and source of the images is clamp | clamp-maven-docker-stage-elalto | mariadb:10.5.4 python:2-slim | The versions are a mess; master docker builds are producing 5.1 versions, frankfurt branch 5.0 versions, and el-alto 4.1 versions. However, CSIT master and frankfurt branches are testing versions 4.1 and CSIT does not even have el-alto branch? | |||||||||||||||||||||||||
dcaegen2 | dcaegen2-services-son-handler-master-csit-testsuites dcaegen2-services-pmsh-master-csit-testsuite dcaegen2-services-bbs-event-processor-master-csit-bbs-testsuites dcaegen2-pmmapper-master-csit-pmmapper dcaegen2-master-csit-testsuites dcaegen2-master-csit-prh-testsuites dcaegen2-collectors-restconf-master-csit-testsuites dcaegen2-collectors-hv-ves-master-csit-testsuites dcaegen2-collectors-datafile-master-csit-ManagementInterface-suite | dcaegen2-services-son-handler-master-merge-java dcaegen2-services-pmsh-docker-merge-master dcaegen2-services-master-bbs-event-processor-merge-java (pmmapper has no trigger job) dcaegen2-collectors-ves-master-merge-java dcaegen2-services-prh-master-merge-java dcaegen2-collectors-restconf-master-merge-java dcaegen2-collectors-hv-ves-master-merge-java (datafile CSITs have no trigger jobs) | nexus3.onap.org:10003/onap/org.onap.dcaegen2.services.son-handler:latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pmsh:latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.components.bbs-event-processor:latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pm-mapper:latest nexus3.onap.org:10003/onap/org.onap.dcaegen2.collectors.ves.vescollector:latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.prh.prh-app-server:latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.restconfcollector:latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.hv-ves.hv-collector-main:latest nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.datafile.datafile-app-server:latest (all hardcoded in various places in the tests) | Some of the triggering jobs produce the tested images, others do not produce any image; requires a deeper look | A lot of simulators used, TBD | |||||||||||||||||||||||||
dmaap | dmaap-buscontroller-master-csit-ssl dmaap-buscontroller-master-csit-with_dr dmaap-buscontroller-master-csit-with_mr dmaap-datarouter-master-csit-ssl-dr-suite | dmaap-datarouter-maven-docker-stage-master (other jobs have no trigger jobs) | nexus3.onap.org:10001/onap/dmaap/buscontroller nexus3.onap.org:10001/onap/dmaap/datarouter-prov nexus3.onap.org:10001/onap/dmaap/datarouter-node nexus3.onap.org:10001/onap/dmaap/datarouter-subscriber (all hardcoded, version not given so latest by default) At least three different source repositories: dmaap/messagerouter/messageservice | There are no jobs producing onap/dmaap/buscontroller - the latest image in Nexus has been updated Thu Feb 21 2019 and belongs to Casablanca (?!) - ticket raised:
| TBD | It's unclear in some of these suites if datarouter and messagerouter are dependencies for buscontroller or components under test? We seem to have multi-repository problem here that needs to be solved somehow | ||||||||||||||||||||||||
multicloud | multicloud-master-csit-functionality1 | - | nexus3.onap.org:10001/onap/multicloud/vio:1.4.1 nexus3.onap.org:10001/onap/multicloud/framework:1.4.1 nexus3.onap.org:10001/onap/multicloud/openstack-starlingx nexus3.onap.org:10001/onap/multicloud/vio (all hardcoded, default latest for those that do not define version explicitly) | Latest in Nexus: onap/multicloud/vio:1.4.1 is from Sep 12 2019 onap/multicloud/framework:1.4.1 is from Sep 06 2019 ...these seem to be some early El-Alto versions? Ticker raised: https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-maven-docker-stage-elalto produces version 1.4.3 of onap/multicloud/openstack-starlingx https://jenkins.onap.org/view/multicloud/job/multicloud-framework-maven-docker-stage-master produces version 1.6.0 (and also latest) of onap/multicloud/framework multicloud-openstack-maven-docker-stage-master produces version 1.5.6 (and also latest) of onap/multicloud/openstack-starlingx multicloud-openstack-vmware-maven-docker-stage-master produces version 1.4.2 (and also latest) of onap/multicloud/vio | - | |||||||||||||||||||||||||
music | music-master-verify-csit-music-distributed-kv-store-test-plan | music-distributed-kv-store-master-docker-golang-shell-daily | nexus3.onap.org:10001/onap/music/distributed-kv-store (hardcoded, latest by default) | music-distributed-kv-store-master-docker-golang-shell-daily | - | Basically OK (even though default reference to latest is fragile) - the only issue is the same as with all the other jobs with valid job triggers; both the CSIT and its triggering docker build are executed daily; does that make any sense (the CSIT runs therefore two daily scheduled runs)? | ||||||||||||||||||||||||
oom-platform-cert-service | ||||||||||||||||||||||||||||||
optf | ||||||||||||||||||||||||||||||
policy | ||||||||||||||||||||||||||||||
sdc (special case) | ||||||||||||||||||||||||||||||
sdnc | ||||||||||||||||||||||||||||||
so | ||||||||||||||||||||||||||||||
usecases (disabled?) | ||||||||||||||||||||||||||||||
vfc | ||||||||||||||||||||||||||||||
vid | ||||||||||||||||||||||||||||||
vfsdk |
...