Versions Compared

Old Version 43

changes.mady.by.user Prithivraj

Saved on

compared with

New Version 44

changes.mady.by.user Prithivraj

Saved on

Key

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

...

System Config Param

Description

DEFAULT_SYNDICATION_PARTNER

Default syndication partner. Eg: Company name

SYNDICATION_PARTNERS

Syndication partner names in comma separated format.  Eg: Company name1, Company name2

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, 2DAYS, FAST_QUICK, FAST_QUICK_CI. New test types can also be created here using comma separated format. 

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

MINIMUM_FAIL_PERCENTAGE_TO_RETRY_TEST

After test execution, orchestration will calculate the percentage of failed test steps in a test script. If the failure percentage is beyond the limit configured here, then test 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

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; Required only for integration with Partner's CI Portal
RDK_PORTAL_AUTHAuthentication token to access the RDK portal. Currently, this is not used by Orchestration for communication
ISSUE_MANAGEMENT_URLIssue/Defect Management service base url; Required only for automated defect creation
AUTOMATICS_BASE_URLBase URL of Automatics Orchestration Application
MICROSERVICE_URLBase URL of Scriptless Service
TEST_TYPE_MAPTest types enums are removed from orchestration and added here as key value pairs. Use the insert script from Automatics_DB.sql mentioned with a comment as 'Changes for Test type configuration' to insert this record.

 

Device Models

...

Job templates are created . If it is not not created you can follow Automatics Orchestration User Manual - Preferred Program - RDK Central Wiki
User can create a new test type, map the test cases to the newly created test type and execute the test cases. To create a new test type add the test type using system configuration tab
under 'Test_Types' configuration name. If a new test type is created, then a new job as to be created based on test type name. The job name should be in the format of 'AUTO_'+'Test type name'+'_TEST_JOB'.
For example If a test type is created as 'SANITYREGRESSION', then the job name should be 'AUTO_SANITYREGRESSION_TEST_JOB'. Do not create new test types by using the use the test type name that are already present
in 'Test_Types' and 'TEST_TYPE_MAP' config values from the system_config table.

Test TypeTemplate Job Name
QUICK, FAST_QUICKAUTO_QUICK_TEST_JOB
QUICK_CI, FAST_QUICK_CIAUTO_QUICK_TEST_JOB_CI
1HOURAUTO_1HOUR_TEST_JOB
4HOURAUTO_4HOUR_TEST_JOB
2DAYSAUTO_2DAYS_TEST_JOB
Tests not mapped to any groupAUTO_COMPONENT_TEST_JOB

...