POC - Scenario 

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.

Use Case

New UI Screens 

Following UI Screens are required to be added in Orchestration

CD Router Test Trigger Page

• To trigger an execution job in CDRouter, we can use webAPI mentioned in below link.  

On success, it will return 200 response code and status of execution will be Pending initially.

• • https://support.qacafe.com/cdrouter/cdrouter-web-api/jobs#launch-a-job

CD Router Job Manager Screen

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:

• Download execution logs of a job
  • https://support.qacafe.com/cdrouter/cdrouter-web-api/results#download-logdir-archive

 CD Router Results Page

• To get execution result of job, we can use webAPI mentioned in below link 
  • https://support.qacafe.com/cdrouter/cdrouter-web-api/results#get-a-result

Config Manage Page

From this page, user can view configs in CD Router

• To get config details, we can use the web API mentioned in below link.
• https://support.qacafe.com/cdrouter/cdrouter-web-api/configs#list-configs

Package Manage Page

From this page, user can view packages in CD Router

• To get package details, we can use the web API mentioned in below link.
• https://support.qacafe.com/cdrouter/cdrouter-web-api/packages#list-packages

DB Structure

Adding 2 new tables to automatics DB:

Reference CD Router Web APIs:

https://support.qacafe.com/cdrouter/cdrouter-web-api/