RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Page History
| Table of Contents |
|---|
Interaction of Automatics Orchestration with CDRouter
...
No Jenkins resources are needed for triggering test execution.
CDRouter and Automatics in CI/CD Pipeline
- User Triggers CDRouter test from Automatics CI environment.
- Then Automatics Orchestration gets the required details from Automatics DB and device details from Device manager and then sends trigger request to CDRouter microservice which again sends the request to device manager.
- Then device manager sends the response to CDRouter microservice and then the microservice sends the trigger request to CDRouter device, where execution of the testcase happens.
- Then CDRouter sends the test results response to CDRouter microservice.
- Then CDRouter microservice updates the result in the CI environment where user can see the end results from Job manager page.
CDRouter in CI Pipeline Use Cases
Execution from Automatics Orchestration
...
CDRouter Support in UI Pages Screens
| Existing Pages | Purpose | Changes Expected |
|---|---|---|
| Trigger Execution Manually Page | User can select CDRouter packages trigger executions | New Drop Down for selecting CD Router Tests via Test Source |
| Job Manager Page | User can view the progress of CD Router package executions - Each job will show the status of single package | No change in UI |
| Execution Results Page | To view overall execution results like Total script count, and its pass and fail count | No change in UI |
| Detailed Execution Results Page | To view the execution results of each test script (in cd router each test case contains only one step) | No change in UI |
| Manage script page | To map cdrouter package with automatics automation id | No change in UI |
CDRouter Rest APIs
Following Rest APIs from CDRouter side are used in service
...
Overview
Community Forums
Content Tools
Tasks