RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
<Work In Progress>
Following diagram shows interaction of Orchestration tool with CD Router Automation Engine via CD Router Service.
Advantage: No Jenkins resources are needed for triggering test execution.
Following diagram shows the interaction among Automatics CD Router service and CD Router Automation Engine
In the request filter page, new tab CDRouter Tests will be coming where user can select CDRouter Tests for CI/CD integration
After CDRouter automation ids are selected, they are displayed in the main page of E2E RDK Request Filter Page.
From the Trigger Execution Manually Page, user can select the CDRouter tests for execution.
Following UI Screens are required to be added in Orchestration
On success, it will return 200 response code and status of execution will be Pending initially.
We can use API mentioned in below link, to get the status of jobs. When execution status changes to running, in the response of this API, we will get the result id. Using result id, we can get the result details of the job.
We can think of background thread checking for updates of running jobs from cdrouter.
https://support.qacafe.com/cdrouter/cdrouter-web-api/jobs#get-a-job
To download execution logs, we can use API mentioned in below link:
From this page, user can view configs in CD Router
From this page, user can view packages in CD Router
Adding 2 new tables to automatics DB: