RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Follow Steps below to install Java 1.8 on CentOS/linux.
Sample output:
Follow below steps to install and configure MySQL on CentOS/linux
Go to the Download MySQL Yum Repository page (https://dev.mysql.com/downloads/repo/yum/) in the MySQL Developer Zone.
Select and download the release package for your platform.
Install the downloaded release package with the following command, replacing platform-and-version-specific-package-name
with the name of the downloaded RPM package.
$> rpm -ivh platform-and-version-specific-package-name.rpm
Example Output:
To start MySQL Service, run command "systemctl start mysqld".
To stop MySQL Service, run command "systemctl stop mysqld".
To restart MySQL Service, run command "systemctl restart mysqld".
To get status of MySQL Service, run command "systemctl status mysqld".
Follow below Steps to setup Tomcat server on CentOs/linux.
Download Apache Tomcat archive file from Apache Tomcat Download Webpage. You can use below wget command to download it.
Example:
Sample Output:
Follow below steps to setup maven on Centos/linux.
Extract distribution archive in any directory.
Example:
-DAutomatics -DhibernateUI.config.file = {path to hibernate config file}
Add the following param to JAVA_OPTS inside apache-tomcat/bin/catalina.sh file
-DloggerUI.properties.file = {path to log properties file}
-Dlog4j.configurationFile={path_to_custom_log4j2-test.xml}
./startup.sh
The system configuration page has following parameters and partner has to configure values for their environment. The description of each parameter is provided below which helps to configure them.
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 |
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_PORTAL | Ideally 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_URL | RDK Portal base url; Required only for integration with Partner's CI Portal |
RDK_PORTAL_AUTH | Authentication token to access the RDK portal. Currently, this is not used by Orchestration for communication |
ISSUE_MANAGEMENT_URL | Issue/Defect Management service base url; Required only for automated defect creation |
AUTOMATICS_BASE_URL | Base URL of Automatics Orchestration Application |
MICROSERVICE_URL | Base URL of Scriptless Service |
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.
For Automatics to use devices from partner's inventory, device groups have to be configured. The device group name in inventory should be added here so that user can execute tests on devices within these groups only. Admin user can map device groups to users so that only those users mapped to device group can execute tests on device.
User can configure Jenkins details in resource details. The test execution happens at jenkins. The jenkins job name should be configured in 'System Configuration' page for param 'JOB_NAME_PREFIX'.
Admin user has to configure source repositories of test projects in Automatics Orchestration.
User can update source repo details via DB. UI support is not available now.
Following are the source repository details to be configured for RDKB. Please execute following SQL Queries.
Configure generic core tests
insert into source_code_details (NAME, CATEGORY_TYPE, SOURCE_REPO, SOURCE_BRANCH, DELETED_DATE, UPDATED_BY, UPDATED_DATE) values ('RDKB_CORE_TESTS', 'RDKB', 'generic-automation-tests', 'rdk-next', NULL, 'admin', now());
Configure RDKB tests
insert into source_code_details (NAME, CATEGORY_TYPE, SOURCE_REPO, SOURCE_BRANCH, DELETED_DATE, UPDATED_BY, UPDATED_DATE) values ('RDKB_TESTS', 'RDKB', 'rdkb-tests', 'rdk-next', NULL, 'admin', now());
Following are the source repository details to be configured for RDKV. Please execute following SQL Queries.
Configure generic core tests
insert into source_code_details (NAME, CATEGORY_TYPE, SOURCE_REPO, SOURCE_BRANCH, DELETED_DATE, UPDATED_BY, UPDATED_DATE) values ('RDKV_CORE_TESTS', 'RDKV', 'generic-automation-tests', 'rdk-next', NULL, 'admin', now());
From Automatics UI,User can navigate to the page Settings -> Job Settings.
And verify (AUTO_QUICK_TEST_JOB, AUTO_QUICK_TEST_JOB_CI, AUTO_1HOUR_TEST_JOB, AUTO_4HOUR_TEST_JOB,AUTO_2DAYS_TEST_JOB,AUTO_COMPONENT_TEST_JOB,) jobs are created in the UI.
If job is not created please follow this Url Automatics Orchestration User Manual - Preferred Program - RDK Central Wiki
If the jos not configured you can follow the UI.
For the below test types configured in Automatics, user has to create a Job template from Job Settings page. The Job names and test types names should be configured as below.
Job templates are created . If it is not not created you can follow Automatics Orchestration User Manual - Preferred Program - RDK Central Wiki
Test Type | Template Job Name |
---|---|
QUICK, FAST_QUICK | AUTO_QUICK_TEST_JOB |
QUICK_CI, FAST_QUICK_CI | AUTO_QUICK_TEST_JOB_CI |
1HOUR | AUTO_1HOUR_TEST_JOB |
4HOUR | AUTO_4HOUR_TEST_JOB |
2DAYS | AUTO_2DAYS_TEST_JOB |
Tests not mapped to any group | AUTO_COMPONENT_TEST_JOB |
Automatics Orchestration has the support to update test execution details and other updates to users via automated email notification.
To enable this feature, admin user has to configure following fields in System Configuration page:
System Config Param | Description |
---|---|
MAIL_FROM | Email sender id |
SMTP_HOST | SMTP server host details eg: {smtpHost:port} |
Following features should be given permission only to Admin.
Admin can upgrade the Automatics by going to Settings -> Upgrade Automatics
Automatics provides support for automated deployment.
Admin can manage all the users of the Automatics.
Admin can Add/Delete the user details and groups. Also, manages the user group module access.