RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Introduction
Automatics supports CI integration and validation of RDK builds. To integrate Automatics in any CI system, the CI portal has to follow REST communication with Automatics.
Automatics has pre-configured filters for CI requests. If request parameters from CI portal matches with filter, then the request is ACCEPTED. For ACCEPTED requests, Automatics will trigger test execution based on test strategy configured in filter. The status of requests can be either ACCEPTED or REJECTED.
CI Portal - Automatics Communication Diagram
Configuring RDK Filters
CI portal should provide details like image name and other details along with REST request. These parameters are configured in RDK E2E Filter.
Default filter parameters expected from CI request are shown below. These parameters except 'images' are configurable from DB. So partner can configure their custom parameters in CI request.
| Param Name | Description |
|---|---|
| images/buildName | [ image names in comma separated format ] |
| buildTask | Build Task eg: CI. NG etc |
| packageType | Image format |
| changedComponents | [ changed components in comma separated format ] |
| buildType | Build Type |
| branches | RDK build branch name |
Details on configuring RDK filters and RDK E2E Requests are available at Automatics Orchestration User Manual#RDKE2EManager
Overview
Community Forums
Content Tools
Tasks