RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
Property | Description |
Mandatory Properties | |
device.props | Holds url that renders device_config.json Url format - {protocol}://{host}:{port}/AutomaticsProps/deviceProps.json Core uses this property to fetch configuration on device models. |
automatics.url | Holds base url of Automatics orchestration Url format - {protocol}://{host}:{port}/Automatics/ Core uses this property to update results back to orchestration. |
regex.test.log | This is used for Html report generation in Jenkins. Default value to be configured is “core\\.test”. The regular expression to identify java package for tests |
regex.utils.log | This is used for Html report generation in Jenkins. Default value to be configured is rdkutils\\.” . The regular expression to identify java package for utils project which is part of RDKV and RDKB automation tests. |
regex.package.log | This is used for Html report generation in Jenkins. Default value to be configured is \\|com\\.automatics.*?.(.*?):.*?](.*) Regular expression for java packages to be considered for html report generation. Those packages that which matches with regex, their logs will be added to html report. User can provide multiple regex values in comma separated format. |
Optional Properties | |
regex.partner.log | This is used for Html report generation in Jenkins. Java package regular expression for partner code. If logs from partner to be considered in html report generation, then this param to be configured. This is optional field |
RACK_BASE_URL | Holds base url for partner’s rest-based implementation of device management or hardware providers like PowerProvider. Url format - {protocol}://{host}:{port}/ This property is required if partner prefers to go with rest-based implementation of device management or hardware providers like PowerProvider. |
partner.impl.deviceManager | By default, Automatics core expects rest-based implementation of device management. However, if partner prefer to go with Java implementation of device management for Core, then this property should be set to true. Orchestration always expects device management APIs in rest only. So in this case, partner has to provide rest implementation for API for orchestration and Java API implementation for Core separately. |
partner.impl.powerProvider | By default, Automatics core expects rest-based implementation of hardware providers like PowerProvider. However, if partner prefer to go with Java implementation of PowerProvider, then this property should be set to true. |
partner.impl.ocrProvider | By default, Automatics core provides default implementation of Ocr provider APIs. However, if partner prefers to go with custom implementation of OcrProvider, then this property should be set to true. |
partner.impl.snmpFactoryProvider | By default, Automatics core provides default implementation of SNMP v2 and v3. However, if partner prefers to go with custom implementation of SnmpProvider, then this property should be set to true. |
crash.analysis.enable | Default value false. When set to true, enables crash analysis during trace monitoring |
crash.analysis.exclusionlist | Can configure test automation ids to be excluded from crash analysis |
alternative.minidump.filename.matcher | Regex to identify mini dump crash file from device log |
alternative.coredump.filename.matcher | Regex to identify core dump crash file from device log |
dump.data.buildId.matcher | Regex to identify build id from device log |
issue.management.enable | Default value false. When set to true, automated issue ticket will be created when a crash occurs. |
issue.management.service.url | Base url of issue management(eg: Jira) service |
WEBPA_SERVER_URL | WebPA server url for webpa related communication eg : https://{host_name}:{port}/api/v2/device/mac: |
serverConfig.path | Core provides default implementation for ssh connection. To make ssh connection to destination, credentials are required to be configured in file server-config.xml and it can kept in any location in Jenkins VM. The path of the file can be configured via property 'serverConfig.path'. Core will use this file to read credentials for ssh login. Template of server-config.xml - server-config.xml |
Login Page
Automatics Properties page will be displayed upn on login. Following are the default properties.
...