Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

CI portal will should provide details like image name and other request params parameters along with REST request.
Automatics has pre-configured filters for CI requests. If request params parameters from CI portal request matches with filter, then the request is ACCEPTED. For ACCEPTED requests, Automatics will trigger test execution based on test data configured against filter.

The status of requests ACCEPTED and REJECTED are available in Automatics Orchestration.

Filter params parameters supported are shown below. These params execpt parameters except 'images' are configurable from DB. So partner can configure their custom parameters in CI request.

Param NameDescription
images/buildName [ image names in comma separated format ]
buildTaskBuild Task eg: CI. NG etc
packageTypeImage format
changedComponents[  changed components in comma separated format ]
buildTypeBuild Type


CI Portal - Automatics Communication Diagram


draw.io Diagram
bordertrue
diagramNameCI_Flow
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth449
revision1



CI Portal

...

- Automatics Communication

  • Rest based communication
  • Automatics End Point: /Automatics/handleRdkTrigger.htm
  • Description: Automatics accepts request from CI portal in this end point. Upon receiving the request from CI portal, Automatics immediately returns the response code 200  200 with response text 'Request received and taken for processing.'  On receiving the request, Automatics will start processing it. Based on the filters configured in Automatics Orchestration, the request from CI portal will be accepted or rejected. 
  • Response Code: 200
  • Response Body: Request received and taken for processing.

Automatics

...

- CI

...

Portal Communication

  • Rest based communication
  • CI Portal End Point: /json/test
  • Description:  When a request from CI portal is accepted, Automatics Orchestration will send execution request to Jenkins. The test cases to be executed for CI validation will pre-configured  in Orchestration. Set of scripts to be executed for a CI request with image name and other param values is configured in Automatics.Upon completion of test execution, the results will be updated back to CI portal.
  • Request Content-Type: application/json
  • Request Body Format:

...