Jenkins Job for Test Execution

In Automatics, test execution happens within Jenkins. Please follow below steps to create and configure Jenkins Job for test execution.

  1. Create Jenkins Job

• From Jenkins, select option “New Item” and specify name of the job to be created and select “OK”. The job name should be similar to one configured in Automatics Orchestration for parameter 'JOB_NAME_PREFIX' in System Configuration page. For eg: If job name configured in Orchestration is 'AUTO_JOB', then job name to be provided should be AUTO_JOB1. More jobs can be created for test execution depending on the number of devices available for testing, number of parallel executions required and system resources. Subsequent jobs will have names as AUTO_JOB2, AUTO_JOB3 etc and they can be created by cloning the initial job.
• Update the total count of jobs created for test execution in Automatics Orchestration in Resource Details Page for parameter 'Maximum Parallel Jobs'. Automatics Orchestration Setup#ResourceDetails

2. Configure Jenkins Job

• Click on newly created Jenkins job and click on Configure option. Job configuration can be edited now.

Steps to be taken care during job configuration.

In General section

• Check the “Discard old builds”.
• Select Log Rotation and we can keep the days of build and Max # of builds.
• Please configure following String build parameters in job.

  
  

  Build Parameter	Description
  filterTestIds	Provides test script ids for execution in comma separated format
  filterTestType	Provides test type to which test scripts belongs to
  updateRdkPortal	If execution result to be updated to CI portal, then this will set to true, other wise false.
  settopList	Provides device mac addresses on which test to be executed in comma separated format. For non-qt tests, only one device can be provided for execution. For qt tests, multiple devices can be provided for execution.
  JMD_ID	Provides the Job Manager Id. This is for identifying each execution job in Orchestration
  BUILD_NAME	Provides RDK build name.  For non-quick tests, it is expected that device is loaded with this build. And, for quick tests this is the build to be loaded in device as part of quick test.
  executionMode	Provides execution environment details. Some of the expected values are RDKV and RDKB
  gr	Provides the test repository name to be cloned for test execution.
  grb	Provides the test repository branch name to be cloned for test execution.
  end_point	Provides details on type of device used. Valid values are RACK_DEVICE and DESK_BOX

  
  

  • filterTestIds, filterTestType, updateRdkPortal, settopList, JMD_ID, BUILD_NAME, executionMode, gr,grb, end_point
• Under Source Code Management, Select GIT.
  • Specify Repository base url in the format 'ssh://{base_url}:{port}/${gr}', where the path of the repo is provided during test execution via the param 'gr'.
  • Add the branch specifier as '*/${grb}', where the repo branch is provided during test execution via the param 'grb'.
• Under Pre Steps in Build section, please add below

Value of automatics.properties.url will be {automatics_properties_base_url}/automatics.properties

• Click on Advanced option and configure maven option. 
• Click on Apply and Save button.