Configuration of 3.0 Scripts in Automatics

Before configuring scripts, ensure that device models are mapped against corresponding device category in Automatics Orchestration.

1. Execute Jenkins Job for Porting 3.0 APIs in Automatics Core project
2. Execute Jenkins Job for Porting 3.0 APIs in Automatics Scriptless Automation project
3. Execute Jenkins Job for Porting 3.0 APIs in RDKV Test Utils
4. Execute Jenkins Job for Porting 3.0 APIs in RDKB Test Utils
5. Import the json file for Test Utility from <Release page> via Automatics Orchestration
6. Import the json file for Test Scripts from <Release page> via Automatics Orchestration
7. Import the test script details in excel sheet in 1.0 format via Automatics Orchestration

Please follow the below steps to deploy automatics core to Artifact repositories from Jenkins job

1.Creating Jenkins job

• From Jenkins, select “New Item”,
  
• Specify name of the new job to be created.
• Select ‘OK’ button.

2. Configuration of Jenkins Job

Configure General Settings

• In ‘General’ settings, add proper description in the ‘Description’ section
• Check ‘Discard old builds’ checkbox

Configure Source Code Management

• In ‘Source Code Management’, select git and under ‘Repository’ add the repo detail

 eg : ‘https://code.rdkcentral.com/r/rdk/tools/automatics/automatics-core’ and also add the repo credentials

• Also add the branch of the repository in ‘Branches to build’
  

  eg : */rdk-next

  

Configure Build Triggers

• In build triggers section select ‘Poll SCM’ and enter the schedule. By this configuration, there will be a polling to the repo for any changes periodically and if there are any changes then the Jenkins build will be executed
  

  Eg : @hourly means the job will check for any changes in the remote repo for every 1 hour and if there are any changes, then the build will run

  

Configure Build Environment

• In ‘Build Environment’, select ‘Delete workspace before build starts’
  

Configure Build Settings

• In the ‘Build’ settings, Click on ‘Add build step’ and Select ‘Invoke top-level Maven level targets’

• Add the following maven step in the text box
  clean deploy -DaltDeploymentRepository=<id>::default::<Artifact repository path>
  altDeploymentRepository – Specifies an alternative repository to which the project artifacts should be deployed
• Click on Advanced button in ‘Invoke top-level Maven level targets’ and add following maven configuration. In the image shown below, maven settings.xml is place at /mnt/maven directory.  Update the settings.xml path based on its location in partner's VM.

           Reference - https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html

Save the Configuration

• Click on ‘Apply’ and ‘Save’