...
- CSIT suites that test components from multiple project repositories at the same time
- such CSIT tests may have to be separated using additional simulators, or
- project repository structures themselves may have to be reconsidered
- Jenkins templates may have to be redesigned to support unified approach for triggering review branch-specific docker build, CSIT execution and voting chain as part of review verification
- CSITs would become blockers for merging code
- local pre-commit verification should be supported better by common CSIT tools
are all projects and suites mature enough to deal with that?
Project status and readiness at the end of Guilin
Projects with CSIT | CSIT jobs | CSIT job triggers | Tested docker images | Docker build jobs | Docker job triggers | Docker image versions | Dependencies |
---|---|---|---|---|---|---|---|
aaf | |||||||
appc | |||||||
ccsdk (disabled) | |||||||
ccsdk-oran (special case) | |||||||
clamp | |||||||
dcaegen2 | |||||||
dmaap | |||||||
multicloud | |||||||
music | |||||||
oom-platform-cert-service | |||||||
optf | |||||||
policy | |||||||
sdc (special case) | |||||||
sdnc | |||||||
so | |||||||
usecases (disabled?) | |||||||
vfc | |||||||
vid | |||||||
vfsdk |