Versions Compared

Old Version 16

changes.mady.by.user Radhika Sudhakaran

Saved on

compared with

New Version 17

changes.mady.by.user Radhika Sudhakaran

Saved on

Key

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

...

  • Launch  Automatics Orchestration.
  • For the first time, login with username as "admin" without password using Self Authentication.
  • After a successful login, we need to setup the following configuration. Some of the configurations are visible only to admin user. Also, it is recommended to keep configuration related access to be retained only with admin. (eg Access to page 'System Configuration' ).


System Configuration

  • From Automatics UI, go to Settings -> System Configuration page.

...

System Config Param

Description

DEFAULT_SYNDICATION_PARTNER

Default syndication partner. Eg: Company name

SYNDICATION_PARTNERS

Syndication partner names in comma separated format.  Eg: Company name

DEVICE_INVENTORY_BASE_URL

Base URL which is having the rest implementation of device management

EXECUTION_ENVIRONMENT_TYPES

Execution environment types in comma separated format. Supported values are RDKV, RDKB

JUN

Jenkins Username 

JUP

Jenkins Password 

LDAP

LDAP Configuration values

Test_Types

Test Types supported by Automatics, QUICK, QUICK_CI, 1HOUR, 4HOUR, FAST_QUICK, FAST_QUICK_CI

EXECUTION_PRIORITY

Test cases will be executed based on the priority. Default provided values in comma separated format for execution priority are P0,P1,P2,P3

JOB_NAME_PREFIX

Prefix of the Jenkins job name. Depending on the test environment partner can configure multiple jenkins jobs for test execution and they all should have name that is configured here with an index. Default provided value is “GENERIC_RDKM_JOB”. eg: GENERIC_RDKM_JOB1, GENERIC_RDKM_JOB2 ...GENERIC_RDKM_JOBN

RDK_PORTAL_AUTH

Authentication token to access the RDK portal. Currently, this is not used by Orchestration for communication

MINIMUM_FAIL_PERCENTAGE_TO_RETRY_TEST

The percentage limit to test retry the failed tests. Default provided After test execution, orchestration will calculate the percentage of failed test steps a test script. If the failure percentage is beyond the limit configured here, then it will be automatically selected for re-trigger. Default value is 20

USER_DEFAULT_MODULES

Values of the default modules that can be accessed by the guest user. Default provided values separated by hyphen -3-5-6-8-9-13-

MASTER

Comma separated string keywords to identify a build name as master

SPRINT

Comma separated string keywords to identify a build name as sprint

STABLE

Comma separated string keywords to identify a build name as stable

CI_BUILD

Comma separated string keywords to identify a build name as CI build

TM_TYPE

Automatics deployment environment. Valid values DEV or PROD

HEAD_ENDS

Device head end values provided Head ends to which devices are connected. Values added in comma separated format

SERVICE_CI_VERIFICATION_VALUE

Value for service CI_VERFICATION. Supported value CI_VERIFICATION.

SERVICE_FUNCTIONAL_VERIFICATION_VALUE

Value for service FUNCTIONAL_VERIFICATION. Supported value FUNCTIONAL _VERIFICATION.

REASON_TYPES

Reasons for adding/updating/deleting scripts via 'Manage Script' page. Values added in comma separated format

MAX_DAILY_ACCEPTABLE_GRT_BUILD_FROM_PORTALIdeally automatics process one time only the same CI build for a device. If process/execution to be done multiple time on same CI build for same device this property can be configured.
RDK_PORTAL_BASE_URLRDK Portal base url
ISSUE_MANAGEMENT_URLIssue/Ticket Defect Management service base url

...

User needs to configure all device models that is going to execute from Automatics.   

Automatics identifies a device model from its build name. For this, admin user has to configure device model and its corresponding build name. It requires only to map the device model and initial starting sub string of build name. The starting few letters(image prefix) in build name should be unique to a device model and this should be added in 'Image Name Prefix' text.

    • Click on Add Device Name
    • Enter the Device Name.
    • Enter the Image Prefix Name. The build name prefix which will be unique to identify a device model. Automatics identify a device model from the build name.
    • Select the device category.
    • Check-in isClientDevice, if the device is a RDKV client device.

...